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

Annotations already declare readOnlyHint=true and destructiveHint=false, and the description adds real behavior beyond that: binary artifacts return a short-lived download_url instead of text, and there is an inline byte cap. It stops short of describing error behavior for missing artifacts or whether download_url expiry is enforced, so it is strong but not exhaustive.

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?

Three sentences, front-loaded with the core action, then the alternative and the fallback, then the edge case for binary payloads. Each sentence carries distinct information; the API reference link is the only mildly extraneous element.

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 correctly carries the return-shape burden by explaining that text comes back inline and binaries come back as a download URL, and it explains the truncation scenario. Missing only failure/not-found semantics for a read tool whose safety profile is already covered by annotations.

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 each parameter and its constraints. The description adds relational meaning the schema lacks: that lookup is either by artifact_id or by the task_id + name pair, clarifying how the loosely-required parameters combine.

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 and resource (read the text body of an artifact attached to a task) and explicitly contrasts itself with get_task, which only lists artifacts and inlines small bodies. An agent can distinguish it from every sibling without opening a schema.

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?

Names the alternative (get_task) and the exact conditions that select this tool: when a body was truncated or omitted, or when fetching one artifact by id or by task_id + name. It also states the mandatory workflow for synthesizers, leaving nothing to inference.

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