show_stress

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

The description discloses input sources (FRED series), output format, and that it is descriptive only. Given no annotations, it sufficiently covers behavior for a parameterless tool.

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 clear structure: first explains computation, second explains output and nature. No wasted words.

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?

Covers input sources, output format, and nature. Could add update frequency or label thresholds, but adequate for a descriptive index 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?

With zero parameters, the description explains the tool's purpose rather than parameter details. It adds value by describing the computation and output, meeting the baseline for zero-parameter tools.

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 computes an Economic Stress Index from specific FRED series and returns a score and breakdown. This distinguishes it from sibling economic tools like show_macro or show_risk, which likely provide different metrics.

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 implies usage for economic stress assessment but does not explicitly compare to siblings. There is no guidance on when to use this versus show_macro or show_risk.

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