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

Annotations already cover the safety profile (readOnlyHint=true, destructiveHint=false, openWorldHint=false), so the description only needs to add non-obvious context. It does: it discloses the payload composition (eight instruments, five scored dimensions, technical states, absorption ratio), the daily cadence, and that it mirrors a specific public page. It omits any latency, caching or freshness guarantees, but the added content detail is substantive.

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?

A single front-loaded sentence names the source, the resource, the instruments and the metrics, then ends with the cadence. It is dense with useful specifics rather than padding. The score dash formatting and long enumeration make it slightly harder to scan, keeping it just short of 5.

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, the description carries the burden of describing the return value, and it does so well by enumerating instruments, score dimensions and the absorption ratio. Combined with annotations that establish it as a safe read, an agent has enough to call it correctly. Only the absence of routing guidance against sibling regime tools is a gap.

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 the baseline of 4 applies. There is nothing to mis-specify and the description correctly implies a parameterless, fetch-everything call.

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 (the house money-regime monitor) and enumerates exactly what it returns: eight named instruments scored 0-100 across five named dimensions plus an absorption ratio. That is far more specific than a tautology. It does not, however, explicitly contrast itself with close siblings such as get_macro_regime, get_credit_stress or get_factor_regime, so the agent must infer the boundary.

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?

There is no when-to-use, when-not-to-use, or alternative-tool guidance. The only implicit cue is the word 'Daily,' which hints at a recurring cadence but says nothing about selecting this tool over the many other regime/snapshot siblings.

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