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

Discloses highly non-obvious behavior that annotations cannot convey: the tool does not return file bytes, it returns a curl_command that must be run verbatim, and the embedded URL is single-use with a 5-minute expiry. This is exactly the operational detail an agent would otherwise get wrong.

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?

Five short sentences, each earning its place, with the counterintuitive behavior (no file bytes, use the curl command) front-loaded right after the purpose statement. Zero 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?

An output schema exists, so return-value detail is optional, yet the description still explains the unusual JSON/curl_command response shape and its expiry constraint. Nothing needed to invoke and post-process this tool correctly is missing.

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?

Only one parameter, and the description reinforces its meaning ("by UUID"). Schema description coverage is reported low, but the sole parameter is a well-constrained UUID whose meaning is already clear from the field itself, so the description neither adds much nor needs to.

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?

States a specific verb (download) and resource (agreement PDF) plus the identifier type (UUID). No sibling tool does the same thing, and the description makes clear it is the PDF-retrieval path rather than a metadata read like get-agreement.

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?

Gives a clear trigger (download an agreement PDF by UUID) and an explicit exclusion ("Do not call any other file-download tool"), which is genuinely useful routing guidance. It stops short of naming a sibling alternative for the metadata-vs-PDF decision, so it is strong but not fully explicit.

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