show_macro

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

No annotations are present, so the description carries full burden. It discloses the output structure (current value, 30d/90d delta, 5y average) and conditional behavior based on home_currency. It does not explicitly state it's a read-only operation, but that is inferred.

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 extremely concise: only two sentences, front-loaded with the most important information (8 indicators, deltas, average). No redundant or extraneous content.

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 no output schema, the description adequately explains what is returned (indicators, values, deltas, averages) and how the parameter affects output. It is sufficient for a simple tool but could mention data sources or update frequency for completeness.

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% with one parameter (home_currency). The description adds meaningful context: 'USD = no FX line' clarifies a key behavioral nuance beyond the schema's simple description. This enhances the agent's understanding.

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 it provides a curated macro snapshot of 8 specific indicators. The verb 'show' and resource 'macro' are specific, and it effectively distinguishes from sibling 'show_' tools that deal with other domains like balances or benchmarks.

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 macro indicators with FX handling, but lacks explicit guidance on when to use this tool versus alternatives like show_risk or show_regime. No exclusions or context when not to use are provided.

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