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

Annotations declare readOnly=false but destructive=false and idempotent=false; the description adds real context beyond them: revocation preserves history, blocks later access, and blocks replays. That clarifies a non-obvious consequence of a non-destructive-labeled mutation. It doesn't address idempotency semantics of retries, leaving one gap.

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?

Two dense sentences with no filler; the actor-permission rule is front-loaded and the revocation consequence follows. Every clause carries distinct information.

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 mutation tool with a nested input object, no output schema, and 33% schema coverage, the description should say more about outcomes and failure modes (e.g., what happens when a non-creator invites, or what a successful response contains). The revocation consequences are covered, but the rest of the call contract is not.

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 only 33%, so the description must compensate; it does add role/action pairing semantics for the unlabeled enum (creator does invite/revoke, invitee does accept/leave). However, thread_id and agent_id meaning are left entirely to the pattern-constrained schema, and idempotency behavior is only documented in the schema itself.

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 names the specific actions (invites/revokes/accepts/leaves) and the exact actors allowed to perform each, which lets an agent map the action enum to a role. It doesn't differentiate this tool from close siblings such as collaboration_invitations or collaboration_members, which remain ambiguous.

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?

"Creator invites/revokes... only the invited agent accepts or leaves itself" gives implicit authorization guidance for choosing an action. But there's no explicit when-to-use-this-vs-alternative guidance relative to the many other collaboration_* tools, so the agent must infer routing.

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