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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so the safety profile is covered. Beyond that, the description adds the admin-only access requirement and notes that each row carries a 'live prorated price' — a behavioral detail about output content that no annotation or output schema conveys.

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 short sentences with zero padding, front-loaded with what is listed, then who may call it, then what comes back. Each sentence contributes new information.

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 parameterless read tool with no output schema, the definition is nearly sufficient: it establishes scope, authorization, and one key return field. The remaining gap is the lack of any disambiguation from 'list_membership_requests', which matters more here than pagination or ordering details.

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 no parameter semantics to explain and the schema is fully closed. The description correctly spends no words on inputs, which is the right baseline for a no-argument tool.

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 gives a concrete verb and resource: 'Lists open membership upgrade requests on this account,' which is distinctly narrower than a generic request listing. However, it never acknowledges the near-identical sibling 'list_membership_requests', so an agent must guess how the two differ.

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?

'An account admin can call it' supplies a caller constraint but not genuine when-to-use guidance or exclusions. With two closely named listing tools in the sibling set, the definition should have stated which one to choose for pending upgrades versus all requests.

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