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

Annotations already mark this as read-only and non-destructive, so no mutation caveats are needed. The description adds useful response behavior: three parallel representations (presentation.display_markdown, tables, data) and a provenance block with as-of dates and age in days, which helps the agent understand what to expect and how to assess staleness.

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 tightly structured: the first sentence states purpose and value set, the second explains the response representations, and the third covers provenance. It is dense without padding, and every sentence earns its place.

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-parameter, read-only tool with an output schema, the description covers everything an agent needs: what the tool returns, the three formats available, and how to evaluate data freshness via provenance. No invocation steps, constraints, or return caveats are missing.

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?

The input schema has no properties, so there are no parameter semantics for the description to clarify. Since there are zero parameters, the baseline of 4 applies and nothing is left undocumented.

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 verb and resource: 'Get current macro regime' with an explicit three-value enumeration (GREEN/YELLOW/RED) and 'business cycle positioning.' The word 'current' distinguishes it from sibling get_regime_history, and the macro-regime focus separates it from financial-conditions, growth, and inflation indicators.

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 gives no guidance on when to choose this tool over get_regime_history, get_financial_conditions, or other macro siblings. There are no alternatives, prerequisites, or exclusion conditions. The only implied usage comes from the tool's name and purpose, not from explicit guidance.

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