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

Annotations already declare destructiveHint=true and idempotentHint=true; the description goes further by explaining the concrete effect (the pending seat is released without joining the team) and the plan availability. It does not say whether a declined invitation can be re-sent or what happens with an expired/consumed token, which are the remaining behavioral gaps.

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 short sentences, front-loaded with the action and the token source, then limits, then plan scope. Nothing is redundant and the scope statement comes before the exclusions.

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?

An output schema exists and annotations carry the safety profile, so the description only needs the action, the credential source, and the boundaries. All three are present, and the single required parameter is fully covered by the schema.

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% with a single documented token parameter, so the schema carries the parameter burden. The description only restates that the token comes from the invitation link, adding no format, length, or expiration semantics beyond the schema.

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 and resource (decline a team invitation) and pins the scope to the invitation addressed to the user behind this key or connection. The added exclusions (cannot decline another person's invitation, cannot remove an active membership) separate it from siblings like remove_team_member and resend_team_invitation.

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?

Makes clear the tool is driven by the token from the recipient's own invitation link and states two explicit when-not conditions. It stops short of naming the sibling tools to use instead (e.g. remove_team_member for active memberships), leaving that routing to inference.

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