vizcom_download_result

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

Annotations declare readOnlyHint=false, destructiveHint=false and openWorldHint=true, and the description adds the genuinely useful behavioral fact that it never overwrites existing output, which explains the non-destructive hint and clarifies repeated-call safety. It does not say what happens if the prompt's output is not yet complete, which would be the remaining behavioral gap.

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?

One compact sentence with the action and destination front-loaded and the non-overwrite guarantee appended as a qualifier. No filler or redundant restatement of the tool name.

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 should say what the agent gets back — a path, a filename, or confirmation of the new local file — and it does not. The precondition ('completed output') is also left unstated as an actionable check (e.g. poll vizcom_status first), which is a notable omission for a simple single-parameter 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 the single promptId parameter, so the description must carry the load; 'for a prompt' does tie promptId to the prompt whose output is downloaded, but it adds no format, scoping or eligibility detail beyond the uuid type in the schema. Marginal compensation for the coverage 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 pairs a specific verb (download) with a specific resource (completed output for a prompt) and a destination (a new local file), which is far more informative than the bare name. It stops short of naming a sibling such as vizcom_get_result, so the agent must infer the boundary between downloading to disk and retrieving a result directly.

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?

'Download completed output ... to a new local file' implicitly tells the agent to use this when it wants a file on disk rather than an inline payload, and 'completed' signals a precondition. There are no explicit exclusions or pointer to the alternative retrieval tool, so a 4 rather than a 5.

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