Get a registered VirusTotal analysis

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

Annotations already flag readOnly/idempotent, and the description adds non-obvious costs and safety: quota consumption, no polling, untrusted output, and ID not being authorization. This goes well beyond schema and does not contradict annotations.

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?

Four short sentences, each carrying distinct information; front-loaded action and exclusions. No wasted words.

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?

Covers when to use, exclusions, quota, and data trust, but lacks return value shape or parameter format. Since there is no output schema, that burden falls on the description, leaving it incomplete.

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 provides only a title for analysis_id with 0% description coverage, so the description must define it. It implies the ID selects an analysis and warns it is not authorization, but gives no format, example, or source.

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 verb 'Read' plus object 'one analysis' makes the action unambiguous. It explicitly contrasts with 'latest file report', distinguishing it from the get_*_report siblings.

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?

States it reads an existing analysis and explicitly lists what it does not do (poll, upload, initiate), plus quota cost. It does not name the sibling get_*_report tools directly, so not a full 5.

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