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

Discloses highly non-obvious behavior beyond the annotations: the tool does NOT return file bytes, it returns JSON containing a curl_command, the URL is single-use and expires in 5 minutes. Annotations only cover the read-only safety profile; the description carries the critical two-step workflow semantics.

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?

Purpose is front-loaded in the first sentence, followed by tight, high-value sentences on return shape, execution steps, and expiration. Every sentence earns its place with 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?

Despite an output schema existing, the description usefully explains the non-standard return (curl_command) and the execution requirement plus URL expiry. Combined with readOnly annotations, an agent has everything needed to invoke it correctly.

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?

With one parameter and reported schema coverage of 0%, the description compensates minimally by naming it a UUID, matching the schema's uuid format. It adds little meaning beyond the identifier type, so baseline is appropriate.

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+resource ('Download an agreement PDF') and the identifier ('by UUID'), immediately orienting the agent. It further differentiates itself by warning against other file-download tools, so it is distinguishable from siblings.

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 clear operational guidance: use this to download a PDF by UUID and do not call any other file-download tool. It stops short of explicitly contrasting with non-download siblings like get-agreement, so it's clear context without full exclusions.

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