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

Annotations cover the safety profile (readOnlyHint, openWorldHint). The description adds genuinely useful behavioral context the annotations don't: the exact indicator set, the 'flashing' per-indicator semantics, an overall verdict output, and the $0.006 USDC x402 cost per call. No return format or refresh-cadence detail, hence not a 5.

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?

A single dense sentence front-loads the resource and indicator list, with cost appended. Every clause earns its place; a mild readability cost from the long enumeration, but no filler.

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?

For a zero-param, no-output-schema, read-only tool, the description supplies the indicator inventory, the flashing/verdict output shape, and the billing model — enough for an agent to decide and call. Missing only return structure detail, which is partially covered by the indicator list.

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?

There are zero parameters, so the parameter-semantics burden is nil and the baseline is 4. The description correctly presents this as a parameterless dashboard rather than implying hidden inputs.

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 resource (US recession dashboard) and enumerates exactly which indicators it reports (yield-curve inversions, Sahm rule, smoothed probability, Chicago Fed financial conditions, unemployment rise). No sibling tool covers this composite macro-recession view, so it is clearly distinguished.

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?

Context implies 'use this for recession monitoring,' and the description notes the per-call cost, which helps selection. But it never states when to use this versus a narrower sibling like macro_us, economy, fred_series, or rates, and gives no exclusions.

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