/**
 * Per-tool usage guidance for the hand-rolled tools.
 *
 * The five CRUD templates and the tab template compose their own
 * "Quand / Plutôt que" block (see `description-builders.ts`), which covers
 * ~145 of the 182 tools. The remaining ones carry hand-written descriptions
 * whose *body* is worth keeping — endpoint filter vocabulary, the traps
 * documented in CLAUDE.md — and only lack the guidance section. Rewriting each
 * of them into a `composeDescription` call would churn a lot of prose to add
 * two lines, so the two lines live here and are injected centrally.
 *
 * The obvious hazard of a name-keyed side table is silent drift: rename a tool
 * and its guidance evaporates with nothing failing. `usage-guidance.test.ts`
 * closes both directions — no entry may point at a tool that does not exist,
 * and no tool may end up without guidance. So the table cannot rot quietly;
 * it can only break the build.
 *
 * What belongs in `instead`: a **named** sibling and the reason the two are
 * confusable. "See the other tools" is worse than nothing — it costs bytes and
 * resolves no ambiguity. Where a tool genuinely has no alternative, say that
 * explicitly (`boond_expenses_default`, `boond_documents_create`), because
 * "there is no other way to get this" is itself the actionable fact.
 */
export interface UsageGuidance {
    /** When this tool is the right call. */
    when?: string;
    /** The named alternative, and why they are confusable. */
    instead?: string;
}
export declare const USAGE_GUIDANCE: Record<string, UsageGuidance>;
/**
 * Insert the guidance block after the description's first paragraph.
 *
 * Position is deliberate: the purpose sentence stays first (it is the only
 * thing guaranteed to be read in a 182-tool listing), the guidance comes
 * second, and the endpoint's filter vocabulary keeps its place below. That is
 * also the order the composed templates produce, so the whole catalogue reads
 * the same way regardless of which path built the description.
 */
export declare function injectUsageGuidance(description: string, guidance: UsageGuidance): string;
/** Apply the table to one tool config, if it has an entry and no guidance yet. */
export declare function withUsageGuidance<T extends {
    description?: string;
}>(name: string, config: T): T;
//# sourceMappingURL=usage-guidance.d.ts.map