download_status

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

With no annotations provided, the description fully discloses behavioral traits: initial queued status is normal, age_seconds is the metric for cancellation decisions, the message field contains actionable instructions, and stale IDs require re-download. This goes beyond simple status retrieval and prevents misuse.

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?

The description is front-loaded with the core purpose, then structured into bullet-point rules. Every sentence offers actionable value, and the formatting makes scanning easy despite the length.

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?

Given no annotations and no output schema, the description thoroughly covers the download-status lifecycle: when to poll, how to interpret queued status, when to cancel, how to use the message field, and what to do on stale IDs. It equips the agent with necessary edge-case handling.

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?

The schema has one required parameter 'id' with no description, and the description only indirectly references it as 'download ID' in the stale-ID rule. It does not explicitly define the parameter's meaning or source, though context implies it. With 0% schema coverage, this is a modest gap.

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?

The description opens with 'Poll progress of an active or recent download,' using a specific verb (poll) and resource (download status). This clearly distinguishes it from siblings like download, cancel_download, and list_downloads.

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?

Provides explicit CRITICAL TIMING RULES with when-to-use and when-not-to-use guidance, including not calling within 30 seconds, not cancelling on queued status, and following the message field's sleep recommendation. It also specifies actions for stale IDs, offering clear operational context.

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