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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive behavior, lowering the burden. The description adds that results are 'verified' and include quotes/links, plus disambiguation via author+title, but doesn't go into deeper behavioral specifics like auth requirements, rate limits, or edge-case handling. This is modest added context, consistent with a 3.

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, front-loaded with the core action, followed by usage examples and disambiguation guidance. Every sentence serves a purpose—no fluff, no redundancy.

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 single-parameter, read-only tool with an output schema, the description adequately covers purpose, usage, and parameter quirks. It could mention behavior when no recommenders are found or specific formatting of the author+title input, but overall it is sufficiently complete 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?

Schema coverage is 100%, so the schema already documents the title parameter. However, the description adds significant meaning by noting the tool 'Accepts a title ("Sapiens") or author+title for disambiguation.' This clarifies how to handle ambiguous titles, which is not present in the schema's simple 'Book title' 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 starts with a specific verb+resource: 'Return every verified person who recommends a given book, each with their quote about it and a link to the original source.' This clearly distinguishes it from siblings like get_person_recommendations or search_books by emphasizing the output structure and the unique 'signature dataset' angle.

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?

It provides explicit when-to-use examples: 'use it when a user asks "who recommends Sapiens?", "is Zero to One worth reading?", or wants social proof / expert opinions on a specific title.' It lacks explicit when-not-to-use or alternative references, but the context is clear and well-scoped.

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