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

The description goes beyond the readOnlyHint annotation by disclosing the paid nature of the tool, the HTTP 402 behavior when called without payment, and cost scaling for broad vs. narrow queries. It also adds data-quality context (enriched DaedalMap history lane, stable loc_id) that influences trust and interpretation.

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?

The description is three sentences, front-loaded with the key purpose and payment caveat. Every sentence adds value: what it queries, when to use it, and the payment behavior. No fluff or repetition.

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?

For a paid, query-style tool with a good schema and annotations, the description covers purpose, usage, payment flow, cost implications, and data provenance. It is complete enough for an agent to select and invoke the tool correctly without needing to infer major details beyond the schema.

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 baseline is 3. The description does not add significant parameter-level meaning beyond the schema, though it does hint at the need for narrower filters for cost control, which relates to the filters and limit parameters. This is marginal but not enough to raise the score.

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 clearly states the tool queries the published earthquakes_events lane with specific verbs ('Queries', 'Use this first'). It distinguishes itself from sibling tools by describing it as the enriched DaedalMap history lane with stable loc_id geography, not the preliminary upstream wrapper or live earthquakes.

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?

Explicitly instructs to use this tool first for earthquake questions and explains why (enriched, stable loc_id), and contrasts with the preliminary upstream wrapper. However, it does not name alternative sibling tools explicitly (e.g., get_live_earthquake_events), so the exclusions are implied rather than fully spelled out.

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