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

Annotations already declare the operation as read-only, idempotent, and non-destructive. The description adds little beyond that, only restating that it returns quotes with character/series info, which is also covered by the output schema. There is no additional context about rate limits, matching behavior, or edge cases.

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, well-structured sentence that front-loads the action ('Search for quotes') and specifies the resource and output. No unnecessary words or repetition; every clause adds value.

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?

For a simple tool with one parameter, high schema coverage, output schema present, and safety annotations, the description is sufficient. It tells the user what it does and what it returns. It lacks only explicit sibling differentiation, but that is a minor gap given the tool's simplicity.

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 schema description covers the 'anime' parameter 100%, including examples. The description's example ('Attack on Titan') duplicates the schema example, so it adds no new semantic meaning. The baseline of 3 applies because the schema handles parameter documentation well.

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 function: 'Search for quotes from a specific anime series by title' with an example ('Attack on Titan'). It specifies the resource (anime series), the verb (search), and the output (matching quotes with character and series info), distinguishing it from sibling tools like search_by_character.

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 implicitly defines when to use this tool: when you have an anime title. It says 'by title' and includes an example, providing clear context. However, it does not explicitly mention alternatives like search_by_character for character-based searches, so it lacks explicit exclusions.

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