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

Annotations already declare readOnlyHint=true and destructiveHint=false, covering safety. The description adds that it returns a status about paused admissions but does not detail response format or any side effects (which are minimal). Overall it provides basic transparency beyond annotations.

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 a single, focused sentence with zero wasted words. It is front-loaded with the verb and resource, making it highly scannable.

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 simple read-only boolean check, the description is adequate but lacks an explicit return type. Without an output schema, the agent must infer that it returns a boolean; stating this would improve completeness. The tool's simplicity and annotation coverage mitigate the impact.

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 input schema has one optional generic 'params' object for raw JSON, with 100% schema coverage but no specific parameter definitions. The description does not explain what parameters, if any, are expected, leaving agents without guidance on how to use the param field.

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 clear verb ('Read') and a specific resource ('whether chargebackable intent admissions are paused'). It is distinguishable from siblings like peer_stake_chargeback_enabled and peer_stake_state because it targets the paused status specifically, though it does not explicitly name alternatives.

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 no guidance on when to use this tool versus alternatives, such as when to check before submitting an admission or how it relates to peer_stake_state. Context is purely implicit from the name.

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