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

Annotations already cover read-only, idempotent and open-world behavior, so the description is free to add the non-obvious operational facts: that the call is free, the license state is cleared_with_attribution, and attribution to five named sources is required. It does not state update cadence, freshness lag or failure behavior, which is the remaining gap for a 'slow-moving' indicator.

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?

Purpose, usage trigger and inputs are front-loaded in the first sentence; cost and license follow. The attribution block is bulky (five agencies plus series IDs) but is compliance-relevant content rather than filler, so it earns its space even though it doubles the length.

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?

With no output schema and no parameters, the description carries the burden of describing the return value, and it does name the flag's three possible states plus the five underlying inputs. It stops short of describing the response structure or how the regime is computed from those inputs, so an agent cannot predict field names or thresholds.

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 takes zero parameters, so there is nothing for the description to disambiguate; the baseline for a no-param tool applies. The description correctly does not invent options or filters.

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 states a specific resource (a single slow-moving macro regime flag with risk_on / neutral / risk_off values) and enumerates the inputs behind it, so the agent knows exactly what it gets back. It implies differentiation from get_market_mood via 'slow-moving' but never names a sibling, so the boundary is inferential rather than explicit.

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?

'Use this when you want one slow-moving macro regime flag' gives a clear selection criterion, and 'slow-moving' implicitly contrasts with faster-moving siblings like get_market_mood or get_catalysts. There is no explicit when-not or named alternative, so an agent must infer the routing.

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