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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, and 'Reading changes nothing' merely restates them. The genuinely additive parts are the ordering ('newest first'), the status vocabulary (confirmed/declined/unanswered, expired/withdrawn) and the caller restriction, which give real behavioral context. With return values already covered by an output schema, the surplus beyond annotations is modest.

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?

It is short and front-loaded with the resource list before the qualifiers. The single sentence runs long and stacks several clauses ('whether ... and whether ...'), which makes it denser than needed, and 'Reading changes nothing' is padding against readOnlyHint.

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 inputs, rich annotations and an output schema, the description covers what is listed, the result ordering and the status meaning, which is enough to call it correctly. It is silent on pagination or result limits for what is presumably a growing list, the one real gap given zero parameters to control volume.

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 fully described, so there is no parameter semantics to explain. Baseline of 4 applies; nothing in the description misrepresents the input surface.

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 opens with a specific verb plus an enumerated resource set ('team invitations, payment record shares and webhook endpoints that API keys and connected apps asked for') scoped to pending states, which implicitly separates it from list_team_members, list_webhook_endpoints and share_payment_record. It never names a sibling tool, so the differentiation is inferential rather than explicit.

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?

It states the access prerequisite ('Only the account owner's API keys and connected apps can list them'), which tells an agent when the call will succeed. There is no explicit when-to-use vs. when-not guidance and no pointer to the sibling tools that list confirmed members, endpoints or shares instead.

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