list_indicators

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

With no annotations, the description must disclose behavior. It states it lists indicators but does not mention idempotency, side effects, or response structure. However, an output schema exists, so return details are not required. Minimal but adequate for a simple read operation.

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?

Very concise: two sentences and one line for args. The first sentence states purpose, the second gives usage guidance, and the parameter is explained clearly. No redundant 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?

Given the simple tool (one optional param, no required) and presence of output schema, the description is nearly complete. It explains purpose, usage order, and parameter options. Could mention that listing is all indicators without pagination, but not necessary.

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 0%, but the description compensates by explaining the 'category' parameter and listing valid values: inflation, employment, etc. This adds significant meaning beyond the schema which only defines type 'string or null'.

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?

Clearly states 'List every US economic indicator this server provides.' Identifies the specific verb (list) and resource (indicators). Differentiates from sibling tools by advising to call this first before using other tools like get_indicator.

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 advises 'Call this first to discover valid indicator names before using the other tools.' Provides guidance on when to use (before others) and optional filtering with category values. No explicit when-not-to-use, but strong usage context is given.

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