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

Annotations already cover readOnly, idempotent, non-destructive and open-world, so the bar is lower. The description still adds real value: 'Never signs' clarifies that despite describing budget signing, this call performs no mutation, and it states where the resulting on/off state and spend are visible to the owner.

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 opening 'Read-only' is well front-loaded, but the single sprawling sentence crams in three enablement channels plus a CLI invocation with a default budget figure — details an agent does not need in order to invoke a read-only status tool. It is dense rather than wasteful, yet not tight.

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 one parameter, rich annotations and no output schema, the description supplies enough: what is reported (verifiers, price, enablement), what is not done (no signing), and where authoritative state lives. Only the exact response shape is left implicit, which is acceptable given the low complexity.

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?

There is a single required parameter with 100% schema description coverage and a documented DID pattern, so the schema carries the semantics. The description only obliquely refers to 'an organisation's', adding no format or validation detail beyond the 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?

The description names a specific resource (an organisation's Pay-for-reviews billing status) and enumerates the concrete facts returned: which verifiers bill each review, the price per review, and enablement state. It is distinguishable from every sibling, none of which touch billing, though the head is a noun phrase rather than a verb, making the purpose slightly slower to parse.

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?

'Read-only' signals the read context, but there is no explicit statement of when to call this versus another tool or what to do if the org has Pay for reviews disabled. The bulk of the text describes how a human would turn the feature on/off, which is adjacent guidance rather than tool-selection guidance.

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