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

Annotations already declare readOnly/idempotent/non-destructive, so safety is covered. The description adds behavior the annotations cannot: a login requirement, a 30-day expiry window, the exclusion rule that existing members and previously-removed users will not appear, and the fact that the agreement body is withheld by default (check currentTerms.bodyLength). That is exactly the beyond-annotation context this dimension rewards.

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?

Four bracketed, front-loaded blocks with no filler; the login prerequisite and scope lead, and the chain and pitfalls follow. It restates includeTermsBody twice (chain step and pitfall), which is a minor redundancy keeping it out of a 5.

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?

Though there is no output schema, the description names the relevant response field (currentTerms.bodyLength) and covers auth, scope, exclusions, and the follow-up workflow. An agent has everything needed to call it correctly and act on the result.

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?

With 100% schema coverage the schema already documents includeTermsBody, so the baseline is 3. The description goes further by stating the default (body not returned), the diagnostic field to inspect (currentTerms.bodyLength), and the trigger condition for setting it true (only when reading the terms to the user), which meaningfully reinforces the parameter.

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 with scope qualifiers: invites sent by other organizations that the user has not yet answered, within a 30-day window. An agent can identify it as a pending-inbound-org-invite lister. It does not explicitly distinguish itself from near siblings like list_my_invitations or list_organization_member_invites, 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?

Gives an explicit composition chain: call this, then if currentTerms exists re-fetch with includeTermsBody=true to read the agreement aloud, then hand off to respond_organization_invite. That tells the agent both context and the next tool. It does not compare against competing list tools, so not a full 5.

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