get_recent_earthquakes

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

Describes returned fields and argument range/default, but does not specify the recency window or any rate limits/auth requirements. Since no annotations, description carries full burden; missing details on time range.

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?

Very concise: two sentences plus parameter list. Purpose is front-loaded, no redundant information.

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?

Explains result fields and parameter, but does not specify time window for 'recent'. Output schema exists so return values are documented elsewhere. Still, could be more precise about recency.

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 has no description for limit parameter, but description adds range (1–10) and default (5), significantly improving understanding beyond schema.

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 it returns recent significant earthquake reports with specific fields (time, magnitude, depth, epicenter, intensity summary). This distinguishes it from siblings which are weather-related.

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 explicit when-to-use vs alternatives, but siblings are weather tools so context implies use for earthquakes. Could mention that it only includes significant earthquakes.

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