usgs_earthquakes_by_region

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

No annotations exist, so the description must fully disclose behavioral traits. It merely states the function without details on pagination, rate limits, data freshness, or whether the query returns all earthquakes or a subset. This lack of transparency hinders correct invocation.

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 concise but overly terse. While brevity is valuable, it sacrifices essential detail. A single sentence suffices for a simple tool but is inadequate for a multi-parameter query 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?

Given 0% schema description coverage, no output schema, no annotations, and 7 parameters, the description fails entirely to provide necessary context. An agent cannot determine the return format, optional parameter behavior, or how to properly construct a region query.

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 7 parameters with 0% description coverage, and the tool description adds no meaning. Parameters like minlatitude, maxlatitude, starttime, and endtime are left entirely unexplained, forcing an agent to infer their significance from names alone.

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 the verb 'Get' and resource 'USGS earthquakes' with a geographic qualifier, distinguishing it from siblings like usgs_earthquake_detail (single earthquake) and usgs_recent_earthquakes (no geographic filter). However, it could be more specific about the geographic filtering mechanism.

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 guidelines are provided. The description does not indicate when to use this tool versus alternatives like usgs_recent_earthquakes or usgs_earthquake_detail, nor does it mention any prerequisites or limitations.

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