transfer_status

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

With readOnlyHint=true already declaring the safety profile, the description's real contribution is the retention constraint — only the last 20 transfers are queryable — which is genuine behavioral context not present in annotations. It does not say what is returned when a transfer_id has aged out or is unknown, nor whether the call is cheap enough to poll, leaving meaningful gaps.

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?

Two short sentences, purpose front-loaded, no filler words. The retention sentence is load-bearing rather than decorative.

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?

For a one-parameter read tool with annotations covering safety and no output schema, the description is nearly sufficient: purpose, the three status states, and a retention limit. The remaining gap — how an agent obtains a valid transfer_id and what an expired ID yields — is minor but real.

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 the single transfer_id parameter, so the description carries the burden of explaining it and does not — there is no indication of the ID's format or that it comes from a prior upload/download call. The retention sentence indirectly bounds which IDs are valid, which is the only added meaning.

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?

Names a specific verb ('Get') and resource ('file transfer') and enumerates the three result states (progress, completion, error), which lets an agent tell it apart from list- or cancel-style siblings such as cancel_transfer. It stops short of explicitly naming a sibling it is not, so it falls just below the top band.

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?

Usage is only implied: the tool is clearly the polling counterpart to upload_file/download_file/cancel_transfer, but the description never states when to call it (polling cadence, before vs. after cancel) or which alternative to pick. The retention note hints at a validity window but does not frame it as guidance.

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