get_macro_context

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

No annotations provided, so full burden falls on description. While 'Get' implies read-only behavior, the description fails to disclose whether this requires authentication, if data is real-time versus cached, potential rate limits, or failure modes when macro data is unavailable.

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?

Single sentence efficiently front-loaded with the action and domain. The colon-separated list of specific metrics is information-dense without being verbose, though slight restructuring could improve scannability.

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 partially compensates by enumerating the specific data points returned (Fed Funds Rate, DXY, etc.), but lacks structural details about the response format, data types, or whether all fields are always present versus optionally null.

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?

Zero parameters present, meeting the baseline of 4. With no input parameters, there are no semantics to clarify beyond the schema, and the description appropriately indicates this is a parameterless retrieval operation.

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?

Clear verb 'Get' and resource 'macro economic context for crypto' with specific output fields listed (Fed Funds Rate, DXY, yield curve, recession probability, net macro impact). Distinguishes from siblings like get_asset_context and get_chain_context by specifying macroeconomic rather than asset-specific or on-chain data, though explicit comparative guidance is absent.

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?

No guidance provided on when to use this versus sibling tools like get_asset_context, get_chain_context, or get_temporal_context. No mention of prerequisites, sequencing, or conditions where this tool is most valuable versus alternatives.

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