tool_get_recent_earthquakes

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

There are no annotations, so the description carries the full burden. It only says 'retrieve current earthquakes of the last N hours' and does not disclose behaviors such as result sorting, pagination, or constraints like the maximum hours (168) or default magnitude. No explicit read-only or safety information is provided.

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 one short sentence with no filler. It front-loads the purpose and is appropriately concise for a simple retrieval tool.

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?

The tool has an output schema and full parameter descriptions, but the description itself is minimal. It does not explain how this tool differs from the many earthquake siblings or provide richer context such as typical use cases. It is adequate for a basic list tool but leaves gaps in differentiation.

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 already covers 100% of parameters with descriptive text (hours, limit, min_magnitude). The description's 'N hours' aligns with the hours parameter but does not add any new meaning beyond what the schema provides. The baseline of 3 is appropriate.

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 'Aktuelle Erdbeben der letzten N Stunden abrufen' clearly states the action (retrieve), resource (earthquakes), and a specific time scope (last N hours). It is specific but does not explicitly distinguish itself from sibling tools like tool_search_earthquakes or tool_get_significant_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?

The description provides no guidance on when to use this tool versus alternatives. It does not mention any context for selecting it over sibling tools such as tool_get_earthquake_count or tool_get_largest_earthquakes, leaving usage entirely implicit.

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