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

Annotations already declare readOnly/idempotent/non-destructive, yet the description adds real value: base64 chunking, org/user/credential binding, expiry, and invalidation on role or session-version change. It stops short of describing error behavior when a download has expired.

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 short sentences, front-loaded with what the tool does, then the decoding instruction, then the invalidation caveat. No 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?

With no output schema, the description correctly covers the chunked return shape and lifetime constraints. The main gap is the absence of offset/length semantics, which is material for a paging tool.

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% for all three parameters (downloadId, offset, length). The description implies chunk iteration ('concatenate chunks until complete') but never explains what offset and length control, their defaults, or the 65536 max, leaving the agent to infer paging semantics from the schema alone.

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 a temporary export / large JSON response) plus the mechanism (base64 chunks). It is clearly distinguishable from the many get_* siblings because it reads pre-generated exports rather than querying domain entities.

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?

Explains the workflow: decode and concatenate chunks until complete, and that downloads expire and are invalidated after role/session-version changes. It gives clear usage context but does not name alternatives or state when not to use it.

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