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

Annotations only cover readOnlyHint and openWorldHint; the description goes well beyond by disclosing the paid-call behavior — $0.02 USDC via x402 on Base mainnet, an unpaid call returning a PaymentRequired challenge, and the exact retry contract using _meta["x402/payment"]. This is critical operational context an agent cannot get from structured fields.

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?

Three dense sentences: coverage first, returned fields second, payment mechanics last. Every sentence earns its place with no filler.

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 compensates by naming the returned sections (capabilities, targeted OT protocols, attributed actor, MITRE ATT&CK for ICS techniques) and fully documents the payment round-trip. An agent has everything needed to call 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?

Schema description coverage is 100% with a single 'name' parameter, so the schema already documents the parameter fully. The description reinforces valid values by listing example names but adds no syntax or format detail beyond that, matching the baseline 3.

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?

States a specific verb+resource ('structured profiles of known ICS malware') and enumerates the covered malware families (PIPEDREAM, TRITON, INDUSTROYER2, etc.), which clearly separates it from sibling lookups like getThreatActor or getActorDossier. An agent can identify the tool without opening the schema.

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 listed names imply the tool is a name-based lookup restricted to a known set of ICS malware, but the description never states when to use it over siblings or what happens for an unknown name. Usage is implied rather than guided.

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