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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), so the description earns credit for adding a data-boundary fact the annotations cannot convey: private source PDF and full-text fields are never returned. The 'bounded' qualifier hints at a truncated result, though it doesn't say what the bound is (abstract length, truncation flag, pagination).

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?

Two short sentences, zero filler, with the primary action and scope front-loaded and the data-exclusion caveat second. Every clause carries information.

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?

With an output schema present and rich annotations, the description needn't enumerate return fields, and it appropriately focuses on the key privacy boundary. The gap is guidance on obtaining a valid slug and on not-found behavior, which matters for the only required parameter.

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 carries the full burden for 'slug', yet it never explains what a slug is, its format, case sensitivity, or where the agent obtains one (search_papers). The only implicit signal is that the slug identifies one paper. This leaves the sole required parameter materially under-specified.

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?

Names a specific verb ('Fetch') plus a specific resource ('bounded public metadata and summary text for one published Blossom paper'), which clearly contrasts with the multi-record siblings like search_papers and aggregate_papers. It stops short of naming a sibling explicitly, so it lands at 4 rather than 5.

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 phrase 'for one published ... paper' implies single-record lookup, which points an agent away from search/aggregate siblings, but this is inference rather than instruction. There is no explicit 'use search_papers to find the slug first' guidance and no note on behavior for unpublished or missing records.

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