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

With no annotations supplied, the description carries the full burden and does so: login is required, authorization is limited to the initiating party, the action is irreversible, the invite disappears from the recipient's to-do list, and non-pending invites will not be retried. Those are the auth, preconditions, irreversibility, and side-effect facts an agent would otherwise have to guess.

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?

It is compact and front-loaded: auth, then authorization scope, then irreversibility, then the parameter source, then the failure-state rules. The semicolon-separated telegraphic style is dense, but nearly every clause adds a distinct constraint, and no sentence is filler.

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 one-parameter mutation with no annotations and no output schema, the description covers the auth requirements, preconditions, reversibility, parameter provenance, and post-call effects. The remaining gap is small: it doesn't say what the agent should expect a successful response to indicate. Because no output schema exists, that is a modest omission rather than a blocking one.

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 0%, so the description has to compensate, and it does the most important part by telling the agent where inviteId comes from: get_collaboration_goal(include=invites). It doesn't restate the format or length limits, but those are already enforced by the schema (minLength 1, maxLength 40).

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?

The description states a specific verb and resource (withdraw a collaboration invitation) plus the exact scope: only the initiating party can do it, and only while the invite is still unanswered. That scope makes it clearly distinct from the sibling respond_collaboration_invite (the recipient's accept/decline path) and from cancel_alliance_invitation (a different resource).

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?

It names the conditions for use (only the target initiator, only unresponded invites) and the explicit exclusion: if the invite is already accepted, declined, or expired, do not retry; check the current state first. It also tells the agent to verify the recipient and confirm before acting, which is exactly the pre-call routing an agent needs.

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