What governs this agent, and where it stands

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

readOnlyHint=true already establishes this is a safe, side-effect-free read, so the bar is lower. The description still adds real behavioral value: it discloses that the tool exposes spend-breaker counters showing how close the agent is to tripping an envelope, which directly informs a risk decision. No auth or rate-limit details, but none are needed for a zero-param read.

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?

Two sentences, front-loaded with the purpose and followed by the usage trigger. The contents list is dense and slightly jargon-heavy ('engine posture', 'liveness') but every item earns its place by telling the agent what it will get back.

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 values, and it does so by enumerating the five categories of information returned. The enumeration is somewhat abstract, but combined with the usage guidance it is sufficient for an agent to know when and why to call it.

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 schema has nothing for the description to explain and the baseline of 4 applies. Nothing in the description conflicts with or duplicates the empty input 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?

States a specific and unusual purpose: the governing rules plus the agent's standing against them, and enumerates the returned content (engine posture, agent status, policies, spend-breaker counters, liveness). That enumeration distinguishes it from siblings like rein_heartbeat or rein_receipts, though no sibling is named explicitly.

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?

Gives concrete when-to-use triggers: 'before a large or unusual payment, or after a denial, to find out what the limits actually are.' This is clear contextual guidance, but it never names an alternative tool or states when this is the wrong call.

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