tenki_get_snapshot_download_url

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

Annotations already establish that this is read-only, idempotent, and non-destructive. The description adds meaningful behavior beyond that: it returns a short-lived pre-signed URL, targets the raw disk image, and depends on a snapshot creation option. It does not disclose what happens if the precondition is unmet, but the annotation coverage lowers that burden.

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 a single sentence that leads with the action and outcome, then tacks on the essential prerequisite. There is no filler or redundancy.

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-only tool with rich annotations, the description covers the purpose, output type, and a key prerequisite. It omits details like URL expiration duration or error behavior, but nothing essential is missing for an agent to invoke it correctly.

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 only defines snapshot_id as a required string with no description. The description indirectly clarifies that this ID refers to a snapshot and adds the store_raw_image requirement, but it does not explain the ID format or how to obtain a valid snapshot_id. With 0% schema coverage, this is partial but not full compensation.

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 clearly states the verb (get), the resource (a snapshot's raw disk image), and the output (short-lived pre-signed URL). It also adds the distinctive prerequisite store_raw_image, which separates it from generic download tools like tenki_get_download_url and preview tools like tenki_get_preview_url.

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 gives a clear precondition for use: the snapshot must have been created with store_raw_image. This frames when the tool is applicable, though it does not explicitly name alternatives like tenki_get_download_url or state a direct 'do not use when' exclusion.

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