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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the description only needs to add context. It adds that the output is Markdown and includes specific sections, and says 'verbatim' indicating exact text. This is useful behavioral context beyond the annotations.

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 relatively concise, with the main action front-loaded. However, it repeats the same information in English at the end ('Read the full text of one document, verbatim, with its citation line'), which is redundant with the Italian text. This wastes a sentence.

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 tool with annotations covering safety and schema covering parameters, the description is fairly complete. It specifies the output format and content, and how to specify the target document. It doesn't mention error handling or edge cases, but those are not essential for a read operation.

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 both parameters. The description adds a bit by explaining that ref can be a URL or an id from bonebenders_search, and gives examples. However, this is mostly redundant with the schema examples, so it adds minimal value.

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 returns the full text of a document in Markdown, listing specific content elements (sections, FAQ, cited sources, revision date, citation format). It distinguishes itself from siblings by accepting a URL or an id from bonebenders_search, making it unambiguous that this is the tool for reading a specific document.

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 implies usage by explaining the input can be a URL or an id from search, which guides the agent to use search first to obtain the id. However, it does not explicitly state when to use this tool over alternatives or when not to use it, though the sibling context makes it clear.

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