Normalised, deduplicated, revision-tracked public-health outbreak events from two verified publisher feeds (PAID $0.05)

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

Annotations already declare readOnlyHint=false, idempotentHint=false, openWorldHint=true, destructiveHint=false, so the safety profile is partially covered. The description adds genuinely useful non-annotation context: it is a PAID call at 0.05 USD via x402 on eip155:8453 with a stated remote route, which an agent needs before invoking. It does not explain why the call is non-read-only or non-idempotent (e.g. whether 'refresh' mutates a cache), leaving a notable gap given those hints.

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?

It is short and front-loads the resource and price, which is good. But the first line is a verbatim copy of the title, so half the text conveys no new information beyond the route and cost sentence.

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?

An output schema exists, so return values need not be described, but for a 7-parameter paid tool with zero schema descriptions the definition leaves too much unresolved: no usage guidance, no parameter formats, and no explanation of the non-read-only behaviour. An agent could not confidently construct a call from this.

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 0% across 7 parameters, so the description carries the full burden and does not compensate at all. Critical ambiguities remain unaddressed: the expected format of 'since'/'until' (only maxLength 64 is given), what 'refresh' actually triggers, and what values 'category', 'geography', and 'source_ids' accept.

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?

The description names a specific resource (public-health outbreak events) with qualifying attributes (normalised, deduplicated, revision-tracked, two verified publisher feeds), so the agent knows what it returns. However, it is a noun phrase with no verb (list/fetch/query) and gives no differentiation from bio siblings such as v1_bio_labcyber_events or v1_bio_catalogue.

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?

There is no statement of when to call this tool, when not to, or which sibling covers an overlapping need. The only actionable cue is the price notice, which tells the agent it costs money but not under what circumstances the spend is warranted.

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