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

Annotations only cover readOnlyHint and openWorldHint, but the description adds material behavioral context the schema cannot: the $0.12 USDC x402 price on Base mainnet, and the exact unpaid-call failure mode (PaymentRequired challenge) plus the retry contract via _meta["x402/payment"]. This is precisely the kind of beyond-annotation disclosure the dimension rewards.

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 sentences, front-loaded with what the tool produces before the payment mechanics. Every sentence serves a purpose, though the x402 retry sentence is dense and could be 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?

No output schema exists, so the description must convey what comes back — it names the brief's components (BLUF, key judgments, ICD-203 confidence) and how output relates to /ot/report. Combined with the explicit payment/retry contract, an agent has everything needed to call and handle the response 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% (actor with ICS examples, sector with examples), so the schema already carries parameter meaning. The description only restates that sector is optional scoping, adding no syntax or format detail beyond the schema — 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 (produces/returns) and resource (analyst brief for a threat actor) and enumerates the content: BLUF, key judgments, ICD-203 confidence assessment. It distinguishes itself from the full report at /ot/report, though it does not differentiate from sibling briefs like getActorDossier or getSectorBrief by name.

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?

Implies usage (decision-ready short brief vs a full report) and notes the optional sector scoping, but gives no explicit when-to-use vs not, and no routing against the many sibling brief/dossier/report tools. Guidance is inferable rather than stated.

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