macro-brief

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

No annotations provided, so description carries full burden. It discloses data source (FRED, free, no auth), model (GPT-4o-mini), and output components. It doesn't mention side effects, but the tool is read-only and benign.

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?

Description is concise with three sentences, front-loading the core function. Every sentence adds value without redundancy.

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?

No output schema, but description compensates by listing output components (regime label, risk, implication, narrative). It mentions using 7 signals and FRED. Could be more explicit about return format, but sufficient for an agent.

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 describes one parameter (style) with 100% coverage. Description adds default ('standard' = 200 words) and alternative ('concise' = 100 words), providing practical detail beyond schema.

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 the tool synthesizes a US macroeconomic briefing from 7 real-time signals and produces a structured output with regime label, risk, implication, and narrative. It distinguishes from sibling tools like consumer-brief or energy-brief by specifying the macro focus.

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 explains that it replaces a multi-step data assembly and LLM chain and is cheaper than Bloomberg summaries, implying it's a quick alternative. It doesn't explicitly state when not to use or list alternatives, but the context is clear given the diverse siblings.

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