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

No annotations are provided, so the description must carry the burden. It only states that results are 'significant' and limited by period, but fails to disclose safety (read-only?), data limits, or any side effects. Minimal behavioral context.

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 extremely concise (one sentence) and front-loaded with key info. However, it omits an explicit verb and could be slightly expanded for clarity without losing brevity.

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 no output schema, no annotations, and a single parameter, the description does not cover many essential aspects: return format, ordering, pagination, or error conditions. The tool seems simple but still lacks completeness for an agent to fully understand its usage.

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 description adds concrete valid values for the 'period' parameter ('week|month'), which are not present in the schema. This is helpful beyond the schema's type and default. However, it does not explain the behavior difference between week and month.

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 'Significant earthquakes only' which indicates the resource and filtering, but lacks an explicit action verb like 'list' or 'get'. Compared to sibling 'list_recent_quakes', it implies a more specific query but does not clearly differentiate behavior.

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 on when to use this tool versus siblings. It does not mention alternatives or provide context such as data freshness or applicability for analysis. The sibling 'list_recent_quakes' likely covers a broader set, but no explicit comparison is given.

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