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

Annotations already declare readOnlyHint, idempotentHint, and non-destructive behavior, so the bar is lower. The description adds useful context beyond annotations: the data source endpoint, that no authentication is required, and that results include direct download URLs. There is no contradiction with annotations.

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 three sentences with no filler. It front-loads the main action and scope, then lists filters, then specifies return values, and finally gives access details. Every sentence carries useful information.

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 read-only catalog search tool, the description covers the purpose, spatial scope, filter options, return fields, data source, and authentication requirements. Combined with a complete input schema and output schema, nothing essential is missing for an agent to invoke this tool correctly.

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 coverage is 100%, so the input schema already documents all parameters thoroughly. The description adds a high-level framing around bounding boxes and optional filters, but does not provide substantive extra meaning beyond what the schema already states.

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 action ('Search the USGS The National Map product catalog within a bounding box'), identifies the resource type (downloadable geospatial data), and enumerates product categories. It also names the returned fields, making the tool's output clear and distinguishing it from siblings like usgs-nationalmap.products.list_datasets.

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 gives clear context: use this tool to search catalog products by bounding box with optional keyword, dataset, and format filters. It does not explicitly state when not to use it or name alternatives, though the sibling list_datasets is referenced indirectly in the dataset parameter schema.

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