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

Annotations already declare readOnlyHint=true, destructiveHint=false, and idempotentHint=true, so safety profile is covered. The description adds behavioral context by describing the returned metadata fields, the full catalogue size (58+), and that it returns estimated datapoint counts. It also explains the relationship to wto.trade.data, which is useful for agent decision-making. 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 well-structured: starts with purpose, lists return fields, then usage guidance, and ends with key indicators. Each sentence contributes unique information without redundancy. It is appropriately detailed for a catalog tool and front-loads the core purpose.

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?

The description is complete for agent use. It covers what the tool returns, how to filter, how it relates to siblings, and provides concrete examples. Since an output schema exists (though not shown), the return format is further specified, and the description aligns with that. Nothing critical is missing 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 descriptions for both parameters. The description adds value by providing concrete category codes (TAR, ITS_M, ITS_S) and their meanings, and clarifies that topic_id can be obtained from wto.trade.topics. It also gives example indicator codes, enhancing understanding beyond the schema.

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 clearly states the tool lists all available WTO time-series indicators with metadata. It specifies the resource (WTO time-series indicators) and the action (List), and distinguishes itself from siblings like wto.trade.data by explaining it identifies indicator codes for data retrieval. The title and description are consistent and specific.

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 explicitly instructs to 'Use this tool before wto.trade.data to identify the correct indicator codes' and mentions using wto.trade.topics to enumerate topic IDs. It also explains filtering options by category or topic, providing clear when-to-use guidance and referencing sibling tools.

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