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

Annotations already provide readOnlyHint, and the description adds substantial context: data source (FRED), methodology (z-scored, trailing 36 months), interpretation (50=neutral), history since 1992, and update cadence. Exceeds annotation coverage without 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 dense but purposeful sentences: the first packs methodology and output fields, the second gives usage triggers and update frequency. No wasted words; front-loaded with the key output.

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?

Without an output schema, the description lists all returned fields. It also covers methodology, data source, update frequency, and usage context. For a single-optional-param indicator tool, this is complete.

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% for the only optional parameter (days), which is well-documented. The description adds no additional parameter semantics, so the baseline 3 applies.

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 it returns a monthly 0-100 US consumer-credit stress score with specific methodology (z-scored vs trailing 36 months) and output fields. The verb 'Returns' plus the precise resource differentiates it from generic sibling tools.

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?

Provides explicit 'Call when' triggers (consumer credit stress, card delinquencies, etc.) and use cases (underwriting tightening, collections). Missing when-not-to-use or alternative tool mentions, so not a 5.

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