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

With annotations already covering read-only, idempotent, non-destructive, closed-world behavior, the description adds useful context: bounded excerpts, citation URL and source note returns, nextOffset continuation, and caveats about transcription errors and editorial summaries. It also explicitly rules out arbitrary websites and private accounts, reinforcing the openWorldHint=false annotation.

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 front-loaded with purpose and usage, followed by return behavior and caveats. Every sentence adds useful information without repetition or filler.

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 read-only tool with rich annotations and no output schema, the description covers purpose, return fields, scope restrictions, and source-quality caveats well. The main remaining gap is fuller explanation of the length and offset 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 description coverage is 0%, so the description must carry parameter meaning. It explains the required url as a canonical URL or path from search_library and implies offset through nextOffset continuation, but it does not clarify length units, defaults, or limits, leaving a clear gap for the optional length parameter.

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 states a specific verb and resource: read a bounded text excerpt from an indexed public theoldways.co page. It clarifies scope by naming the source domain and the need for a canonical URL or path returned by search_library, which distinguishes this from the sibling search tool.

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 clearly routes the agent to use a URL or path returned by search_library and states exclusions: no arbitrary websites, private accounts, or live app access. However, it does not explicitly describe when to use this versus list_collections or other alternatives beyond the URL requirement.

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