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

Annotations already declare readOnlyHint=true and idempotentHint=true, indicating a safe, read-only operation. The description reinforces this by calling it 'Reference material' and does not contradict annotations. However, it adds little behavioral context beyond the annotations, such as whether results are cached or real-time. A score of 3 is appropriate as the description adds topic scope but no new behavioral traits.

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 a single long sentence listing many topics with colons, which is somewhat structured but verbose. It is front-loaded with the main purpose, but the list could be more concise or broken into bullet points. Every sentence earns its place, but the density achieves minimal viable conciseness.

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?

Despite having a simple parameter and high schema coverage, the description does not explain what the tool returns (e.g., text with explanations, code examples, or structured data). Since there is no output schema, the description should at least mention the response format or that it provides detailed tutorials. This omission makes the tool less complete for an agent.

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?

The input schema provides 100% coverage with a single parameter 'topic' that has an enum of all possible values and a description suggesting starting points. The main description lists the same topics but does not add additional meaning beyond what the schema already provides. Therefore, it meets the baseline for high schema coverage.

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 it is 'Reference material for Strudel live coding', specifying the tool's function as a guide for a specific domain. The list of topics gives a comprehensive overview, and the title 'Strudel Reference Guide' distinguishes it from siblings like 'get-music-guide' which is likely a general music reference.

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?

The description does not provide explicit guidance on when to use this tool versus its siblings or alternatives. It only lists topics without explaining under what circumstances to choose it. The input schema includes a hint to start with certain topics, but that is within the schema, not the main description.

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