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

With no annotations, the description carries the full burden, and it does disclose the tool's core behavior: returning national counts grouped by status and state. This is a simple parameterless read-only aggregation, so no side-effect warnings are necessary; only a richer response-format description is absent.

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?

One short sentence contains the key facts: scope, resource, and grouping dimensions. Every word earns its place and the most important information is front-loaded.

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?

For a parameterless summary tool with no output schema, the description gives enough information for an agent to select and invoke it correctly. It could be slightly more explicit about the expected response shape or status values, but nothing critical is missing.

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 tool has zero parameters, and the schema confirms this. Per the baseline rule for parameterless tools, the description need not explain parameters; it correctly focuses on the output instead.

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 a specific output verb ('counts') and resource ('National Superfund') with clear grouping dimensions ('status and state'). Its aggregate nature distinguishes it from more specific sibling tools like superfund_site and site_overview.

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?

The description implies when the tool should be used—when national Superfund count aggregates by status and state are needed—but it provides no explicit when-not-to-use guidance or alternatives. The usage context is inferable rather than stated.

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