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

Goes well beyond the readOnlyHint/openWorldHint annotations by disclosing the paid-call behavior end to end: $0.20 USDC via x402 on Base mainnet, a PaymentRequired challenge on unpaid calls, and the retry with a signed payload in _meta['x402/payment']. It also clarifies that the lookup is deterministic and only the remediation prose is LLM-generated.

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 sentences, front-loaded with the core purpose before the mechanics and pricing. Each sentence carries load, though the payment plumbing could be slightly tightened.

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 does the work of describing the return: a deduplicated roll-up into one aggregate severity rating plus an LLM-written remediation summary. Combined with the payment protocol detail, an agent has enough to invoke and interpret it, though the exact aggregate shape remains unspecified.

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%, so the schema already documents all three parameters thoroughly (including the auto-detection of CVE vs actor tokens and the entity_sector tone-only caveat). The description adds aggregate/dedup output context but no parameter-level detail beyond the schema, so the baseline of 3 applies.

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 and resource — rolling up compliance-gap mapping across multiple CVEs/threat actors in one call — and explicitly contrasts the aggregate behavior with the single-item /ot/compliance mapping. An agent can distinguish it from siblings like getComplianceMapping 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 'multiple CVEs/threat actors in a single call' framing makes the batching use case clear, and the mention of the same compliance_mappings data as /ot/compliance gives context. It does not explicitly name the single-item alternative or state when NOT to batch, so it falls short of full routing guidance.

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