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

Annotations already declare readOnlyHint=true, openWorldHint=true, idempotentHint=true, destructiveHint=false. The description adds the key behavioral fact that returned values are the 'legal filter values' for crs_search/crs_recent, which is beyond the annotations and useful for the agent. No contradiction.

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, front-loaded with the core purpose, then a critical usage warning. No filler; every phrase earns its place.

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?

Complete for a read-only vocabulary listing tool. Safety is covered by annotations, params are fully documented, and the description explains the return nature (lists) and why to call it, making it sufficient for correct invocation.

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% with clear descriptions and enums. The description adds semantic meaning to the facet parameter by mapping topics to the taxonomy, authors to analysts, and product_class to product families, enriching the enum values beyond their labels.

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?

States a specific verb ('lists') and resource (CRS taxonomy with counts), and explicitly ties the values to crs_search and crs_recent, distinguishing it from those siblings. The additional mention of analysts and product families clarifies its full scope.

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?

Explicitly instructs to call before filtering by topic and gives a concrete example of why ('U.S. Trade Policy' vs 'Trade' matches nothing). This provides clear when-to-use guidance and implies it is a prerequisite for topic filtering.

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