usgs_recent_earthquakes

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

No annotations are present, so the description must disclose behavior. It only says 'Get recent earthquakes', implying a read-only operation but does not mention any side effects, rate limits, or data freshness. The agent gains no insight into safety or usage constraints beyond the action word 'Get'.

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 too short and under-specified. It lacks necessary details, making it insufficient for an agent to use the tool correctly. Conciseness should not sacrifice completeness.

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?

With no output schema and only a minimal description, the tool is incomplete. The agent cannot infer what the output format or structure will be, nor does it understand the full behavior of the tool given its three parameters. The description fails to provide essential context for correct invocation.

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 only 33% (period has a description). The tool description adds no additional meaning to the parameters. It does not explain what minmagnitude or limit do, nor does it clarify the period values beyond what is in the 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 states 'Get recent earthquakes from USGS', which identifies the verb and resource but lacks specificity about what 'recent' means and how it differs from sibling tools like usgs_earthquake_detail and usgs_earthquakes_by_region. It does not mention that it returns a list or that it supports filtering by magnitude, limit, or period.

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 provided on when to use this tool versus its siblings. The description does not specify that this tool is best for fetching a list of recent events, while usgs_earthquake_detail is for individual event details and usgs_earthquakes_by_region for region-specific events.

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