earthquake_data

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

The description does not disclose any behavioral traits such as data freshness, rate limits, or what occurs when no data matches. Without annotations, the description provides no information about side effects or operational characteristics beyond the basic purpose.

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 a single sentence, which is concise, but it is underspecified. It could benefit from clarifying the result type without adding significant length.

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 data retrieval tool with three parameters and no output schema, the description fails to explain what the response contains (e.g., list of events, details). The absence of information about required fields (none marked required) further reduces completeness.

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?

The input schema has 100% coverage but parameter descriptions are minimal (e.g., 'Example value: US' for country). The tool description adds no additional context about expected formats (e.g., date format) or how parameters affect the query, leaving the agent to infer usage.

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 states it provides 'near real time earthquake for given country', which indicates the domain but lacks a specific verb (e.g., retrieve, list). It is clear it is earthquake data and distinguishes from sibling weather and pollution tools, but the exact nature of the result (list vs. single event) is ambiguous.

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?

No guidance is given on when to use this tool versus alternatives like forecast_weather or current_weather. There is no mention of prerequisites, limitations, or conditions under which the tool should or should not be used.

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