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

Annotations already declare the safety profile (readOnlyHint, idempotentHint, non-destructive, openWorld), so the bar is lower. The description adds context beyond those annotations: what each catalog entry returns (refresh cycle, available formats, exact title) and the downstream consequence of ordering ('silently ignores'). It doesn't mention pagination or result limits, but the added behavioral context is meaningful.

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 with no filler. The first front-loads the action ('List the USGS National Map dataset catalog') before its dense enumerative list, and the second delivers the critical routing instruction. The catalog enumeration is long, but every item earns its place by telling the agent exactly what the catalog covers.

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 one-optional-parameter list tool with full annotation coverage, the description covers catalog contents, return fields (refresh cycle, formats, exact title), and the prerequisite relationship to tnm_search_products. Since there is no output schema, the return-field disclosure carries extra weight. Minor gap: no mention of pagination or ordering, but this is a small omission for such a simple tool.

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% — the single optional filter parameter is fully documented with semantics and examples in the schema itself. The description's catalog enumeration hints at useful filter values but adds no parameter-level detail beyond the schema, so the baseline 3 applies.

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 verb ('List') and resource ('USGS National Map dataset catalog'), enumerates the catalog's contents (3DEP, US Topo, NHD, NLCD, National Structures, Transportation, Boundaries), and names the output fields (refresh cycle, formats, exact title). It also differentiates itself from tnm_search_products, so an agent can tell them apart without opening either schema.

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 second sentence gives explicit ordering guidance — 'Call this FIRST' — and names the sibling alternative with the exact reason: tnm_search_products needs the dataset title verbatim and silently ignores ones it does not recognize. This is explicit when-to-use/exclusion guidance, not left to inference.

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