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

Annotations already declare destructiveHint=true, idempotentHint=true, readOnlyHint=false and openWorldHint=true, so the safety profile is covered by structured data. The description adds nothing beyond that – it does not say what accepting triggers (e.g., membership creation), whether any action is irreversible, or what authority is required. It largely restates the action enum, so it earns a baseline 3 rather than more.

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?

A single sentence that front-loads the verb and enumerates the three actions with zero filler. Every clause earns its place.

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 four-parameter required mutation with no output schema, the schema and annotations together carry most of the burden (idempotency, version conflict, destructiveness). The description is still thin on consequences – what state changes on accept, whether decline or revoke can be undone, and what the caller receives – so it is adequate but not complete.

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 description coverage is 100% and every parameter is documented in the schema, including the op_key retry semantics and expected_version conflict behavior. The description's only parameter-adjacent content duplicates the action enum's own description. Baseline 3 is correct when the schema does the heavy lifting.

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?

Names a specific verb (respond) and resource (invitation) and enumerates the three supported outcomes: accept, decline, revoke. The distinction between invitations 'sent to you' versus 'one you sent' clarifies the direction of the operation. It does not name or differentiate itself from siblings such as invite or list_invitations, 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?

Usage is implied by the description's mapping of each action to a situation ('sent to you' vs 'one you sent'), but there is no explicit when-to-use guidance, no mention of prerequisites such as first locating the invitation via list_invitations, and no alternatives offered. Adequate but with clear gaps.

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