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

Annotations already declare readOnlyHint, idempotentHint, non-destructive, and closed-world, so the safety profile is covered. The description adds behavior the annotations cannot: results are ordered newest-first, and open requests surface a live prorated price sourced from the rate sheet, which hints at an underlying pricing lookup.

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 the scope and ordering stated up front, followed by a single useful note about request contents. No filler or restated name.

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 no-parameter, read-only lister with no output schema, the description covers ordering and the notable payload detail (live prorated price). The only meaningful omission is the boundary against list_pending_membership_requests, which an agent would need to route correctly.

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 and the schema is empty with additionalProperties=false, so there is nothing for the description to disambiguate. Baseline 4 applies.

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 verb and resource ("Lists ... membership upgrade requests") and scopes it to "this seat," so the agent knows exactly what is returned. It does not, however, distinguish itself from the closely-named sibling list_pending_membership_requests, leaving genuine ambiguity about which list to call.

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 guidance on when this tool applies versus the many adjacent siblings (list_pending_membership_requests, request_membership_change, cancel_membership_request). The reader must infer usage purely from the name and the phrase "this seat."

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