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

Annotations only declare readOnlyHint and openWorldHint, but the description adds critical behavior the agent could not otherwise know: a $0.05 USDC charge per call via x402 on Base, that an unpaid call returns a PaymentRequired challenge, and that the exact same call must be retried with the signed payload in _meta["x402/payment"]. This is exactly the kind of operational context the schema cannot carry.

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 tight sentences, front-loaded with purpose and return contents, followed by the cost and the payment-failure recovery path. Nothing is repeated from the schema and every sentence carries information an agent needs.

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 supplies the return fields; the annotations supply the read-only/open-world safety profile; and the description additionally covers billing and the payment-challenge retry loop. For a 2-parameter read-only lookup, nothing required to call it correctly is missing.

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%: both sector (with its value list) and status (enum active/all) are fully documented in the schema. The description only reuses the sector concept ('targeting a specific industrial sector') and adds no syntax or format meaning beyond it, 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?

Clear specific verb+resource: retrieving active ICS campaigns for a given industrial sector, with an explicit enumeration of returned fields (campaign name, actor, start date, geography, TTPs, CVEs). However, it never distinguishes itself from closely related siblings such as getSectorBrief, getSectorSitrep, or getActorsBySector, so an agent must infer the boundary.

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?

Usage is implied by the name and the sector-scoping sentence, but there is no explicit when-to-use/when-not guidance and no routing to or away from the many sibling sector/campaign tools. The only explicit instructions concern the payment retry flow, which is how to call the tool rather than when to choose it.

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