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

Annotations only declare destructiveHint=true, and the description adds substantial value beyond that: authorization requirements, the state constraint, the concrete effects (accept link and sign-up token stop working, member disappears from list), and that nothing is sent to the invitee. It adds rich behavioral context, but the destructiveHint was already provided by annotations. Note: this is well above the annotation-only floor; a 5 would require return-value or error-handling detail.

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?

Front-loaded with the verb+resource and the key disambiguation, and every sentence earns its place. Slightly dense with parentheticals (shared project, status invited), which is efficient but marginally reduces scannability.

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 destructive mutation with no output schema, the description covers preconditions, effects, notification behavior, and state constraints. Nothing an agent needs to invoke it correctly is missing.

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?

Schema coverage is 100%, so the schema already documents both project_id and member_id, including where each value comes from. The description adds no parameter syntax or format detail beyond what the schema provides, making the baseline 3 appropriate.

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?

Specific verb+resource (cancel a pending shared-project invitation) with an explicit negative disambiguation (— NOT a Slack workspace) and a clear distinction from the invite_to_shared_project sibling. An agent can identify the operation without opening the schema.

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?

States precise preconditions: only the inviter or project owner may act, and only while status is 'invited'. It also states the exclusion ('someone who already joined cannot be removed this way'), implying a different mechanism is required for that case.

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