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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds the org-scoping behavior ('for your organization'), which is genuinely useful, but says nothing about pagination behavior or result volume. Minimal added value over annotations, so a 3.

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 tight sentences with the purpose front-loaded and no filler. Efficient, though it underspecifies rather than being optimally concise.

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 an output schema present and annotations covering the safety profile, the description only needs to cover behavior and parameters. It is adequate on scope but omits pagination semantics and the required queryParams wrapper, leaving gaps for a list endpoint.

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?

Reported schema coverage is 0% and the required queryParams wrapper is undocumented anywhere, so the description must compensate but does not. It names only filter[status_eq] out of five nested properties and its example ('e.g. pending') merely repeats the schema enum, leaving page[size], page[number], filter[access_eq], and filter[source_email_eq] unaddressed.

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?

States a specific verb+resource+scope: 'List invitations for your organization'. An agent can distinguish it from get-invitation (single item). It does not explicitly name a sibling alternative, so it stops short of a 5.

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 only guidance is a filter example (filter[status_eq] = pending), which is parameter help rather than when-to-use. It never says when to prefer this over get-invitation or how it relates to list-users, and gives no exclusions or prerequisites.

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