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

Even with annotations declaring readOnly/openWorld/idempotent and non-destructive behavior, the description adds substantial behavioral context: it composes 16 FRED series with live crypto, runs them in parallel, returns callouts, and crucially warns that components do not share a single date and that each group carries its own as_of map while freshness states the full span. This goes far beyond what annotations provide.

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 long but every sentence carries weight: the indicator list, the parallel computation note, the no-arguments pointer, and the highly important freshness/as_of caveat. It is front-loaded with the core promise and ends with a critical usage warning. No filler or redundant repetition.

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 complex tool with 16 mixed-frequency series, no output schema, and no parameters, the description is exceptionally complete. It explains what is returned (structured dashboard plus callouts), the mixed-date caveat, the existence of per-group as_of maps, the meaning of freshness, and the caution about comparing fields against the top-level as_of. This is sufficient for an agent to invoke and interpret results correctly.

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 tool has zero parameters and the schema already reflects this with an empty properties object. The description adds explicit confirmation with 'No arguments,' which is helpful but not deeply necessary; the baseline for a zero-parameter tool is appropriate.

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's purpose with a specific verb and resource: 'Get the current state of the US/global economy in ONE call.' It enumerates the exact indicators covered and explicitly positions itself as a single-call alternative to fetching ten indicators separately, which distinguishes it from narrower sibling tools like indicator.

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 clear when-to-use guidance: use this for a comprehensive macro snapshot instead of fetching multiple indicators separately. It does not explicitly state when not to use it or name alternative sibling tools beyond the implied single-indicator route, so it falls just short of a perfect 5.

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