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

Annotations only cover the read-only/idempotent/open-world safety profile; the description adds materially more: uncached groups return an error rather than a result and are queued, not charged; the call costs $0.05 USDC via x402 with payment passed in _meta["x402/payment"]; invalid input or upstream failure returns an error and is not charged. These are exactly the operational traits annotations cannot express.

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?

Front-loads the identity and payload inventory, then handles error and payment behavior in the closing sentences; every sentence earns its place. The long nested content list makes the first sentence dense, but nothing is padding.

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?

There is no output schema, yet the description enumerates what comes back, and the pricing, payment channel, and cache-miss/charge behavior complete the picture. An agent has everything needed to decide, invoke, and interpret the call.

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?

A single 'name' parameter with 100% schema description coverage (including examples 'akira, qilin'), so the schema carries the semantics. The description adds nothing about the parameter, and the baseline of 3 applies when coverage is this high.

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?

Names a specific verb+resource ('Threat-hunting profile of one active ransomware group') and enumerates the exact payload: leak-site listings, momentum status, tools, malware, campaigns, ATT&CK techniques, CVEs, headlines, D3FEND countermeasures. It also explicitly differentiates itself from the sibling group_profile, so an agent can separate the two without opening either 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?

States the use context (threat-hunting profile of a group) and names an alternative with its condition ('Use group_profile for its claim sample'). It does not address when to prefer this over other siblings such as recent_claims or cve_intel, but the primary routing decision is explicit rather than implied.

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