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

Annotations already declare readOnlyHint=true, openWorldHint=true, and destructiveHint=false, so the safety profile is covered. The description adds nothing beyond that: it does not disclose that requests default to magnitude 2.5+ filtering, that omitting coordinates yields a global feed, that lat/long/maxradiuskm act as a coupled geo filter, or anything about result volume and rate behavior from the upstream USGS service.

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?

It is a single front-loaded sentence with no wasted words, but it is terse to the point of under-specification rather than being efficiently concise. The space saved is not redeployed toward the behavioral or scoping detail an agent actually needs.

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 seven optional parameters, no output schema, and no required fields, the agent needs guidance on sensible query shapes and on what the response contains. The description supplies neither, leaving the caller to guess whether the tool returns event lists, hazard ratings, or both.

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 100%, so all seven parameters, including defaults for limit and minmagnitude, are already documented in the schema. The description contributes no additional parameter meaning, which is acceptable at this coverage level but is a missed opportunity to explain how latitude/longitude/maxradiuskm must be combined.

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 names the domain (seismic activity, earthquake risk profiles) and the source (USGS GeoJSON), but there is no clear verb: it is ambiguous whether the tool lists earthquake events, returns hazard/risk data, or both. Given the schema's event-style parameters (starttime, minmagnitude, limit), an agent could reasonably infer event listing, but the phrase 'risk profiles' points somewhere else entirely.

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?

There is no when-to-use guidance, no mention of prerequisites, and no exclusions or alternatives. Since no sibling tool covers seismic data, the lack of differentiation is tolerable, but the description still gives no signal about which queries are appropriate – e.g., whether it is for recent-event monitoring versus regional hazard assessment.

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