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

Annotations already declare readOnlyHint and openWorldHint. The description adds that it is 'Powered by semantic search over strudel.cc and ABCJS docs', which provides context about the search mechanism and source authority. 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 three sentences with no fluff. Each sentence adds value: what it does, when to use it, and how it works. Front-loaded with the main action.

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 it's a search tool with two parameters and no output schema, the description covers return content ('code examples and explanations'), usage context, and query formulation guidance. Siblings are referenced appropriately.

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%. The description adds valuable examples for the query parameter ('Good: ... Bad: ...') and explains the library parameter's enum values ('strudel for live coding patterns, abcjs for sheet music notation'). This goes beyond schema description.

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 uses a specific verb 'Search' on a clear resource 'detailed documentation for Strudel live coding or ABC/ABCJS notation'. It distinguishes from siblings by stating when to use this tool over the curated guides.

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 says 'Use this when the curated guides (get-strudel-guide, get-music-guide) don't cover what you need' and names those alternatives. Provides specific scenarios like 'specific functions, advanced techniques, or when you're unsure about syntax'.

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