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

Beyond the annotations (which already declare read-only, idempotent, non-destructive), the description discloses the 200000-character truncation threshold, which formats return inline text versus a link, the exact auth mechanism for the download URL (Authorization: Bearer with the same API key), and the required runs:read scope. The prompt-injection caution that transcript/report content is data is a meaningful behavioral disclosure an agent could not infer from structured fields.

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?

Four dense sentences, front-loaded with the core action, then the return-shape rules, then auth, then the safety note. It is efficiently ordered, though the format enumeration partially duplicates the schema's enum description.

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 no output schema, the description carries the full burden of explaining return values and does so precisely (`content` vs. `download_url`). Combined with the size limit, auth requirement, scope, and ID provenance, an agent has everything needed to call this correctly on the first attempt.

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 baseline is 3; the description earns one above that by tying `format` to concrete consequences (text in `content` vs. `download_url` for csv/xlsx/docx) and adding the character limit that the schema does not state. Some of this repeats the enum description, which caps it below 5.

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?

"Fetches one deliverable of an analysis" names a specific verb and a single, bounded resource, making clear this is a single-item retrieval rather than a listing. It also points at qualitative_list_deliverables as the ID source, which separates it from the list sibling without ambiguity.

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 tells the agent how to obtain the required `deliverable_id` (from qualitative_list_deliverables) and when a follow-up HTTP GET is needed instead of expecting content inline. It does not state any explicit when-not-to-use case or contrast against qualitative_get_run, so it stops just short of full routing guidance.

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