amplify_suggest_pattern_key

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description fully discloses behavior: it returns up to 3 existing keys ranked by trigram similarity, or a new key suggestion if none clear the threshold. It also explains the consequence of not using it (frequency counter never aggregates). No contradictions.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is extremely concise: two sentences that front-load the purpose and then provide usage context and outcome. No wasted words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given no output schema, the description explains the return values adequately. All params are documented, and the tool's behavior and usage context are fully covered. Complete for a suggestion tool with three parameters.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and each parameter has a description. The description adds context by explaining that title and description help disambiguate, and that the tool uses them to find similar keys. This adds meaning beyond the schema, but not extensive format details.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's purpose: to suggest an existing pattern_key or propose a new one for a lesson before recording. It specifies the verb 'suggest' and the resource 'pattern_key', and distinguishes it from siblings by noting it should be used before amplify_learn to prevent key duplication.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly states when to use the tool: 'Use this before amplify_learn when you suspect the lesson is a recurring pattern.' It also explains why (prevents failure of aggregation) and what it returns (up to 3 existing keys or a new suggestion). This provides clear guidance on when and why to invoke this tool.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.