earthquake-intel

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

Discloses return fields (magnitude, depth, location, tsunami flag, shake intensity) and source (USGS). No annotations provided; description adds reasonable context but could mention rate limits or data freshness.

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?

Two sentences that front-load the core purpose and key capabilities. 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?

No output schema, but description lists useful return fields. Covers modes, defaults, and API source. Slightly lacking details on error handling or edge cases.

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 coverage is 100%, so baseline is 3. Description only reiterates default magnitude thresholds already in schema, without adding new parameter meaning.

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?

Clearly states the tool fetches earthquake data from USGS with two modes: recent global significant quakes and location-based quakes. Specifies magnitude thresholds and time/radius. Distinct from siblings like 'usgs-earthquake' by detailing its specific parameters and scope.

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?

Describes when to use each mode (recent global vs. location-based) with specific defaults. Also notes no API key required. Does not explicitly exclude any scenarios or mention alternative tools.

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