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

Annotations already declare destructiveHint=true, so the destructive nature is covered without needing the description to repeat it. The description adds useful context by restricting the action to the trip owner, but it does not disclose effects like reversibility, immediate access revocation, or whether the owner can be removed.

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?

The description is one short, front-loaded sentence with no filler. It conveys the action, target, and an important access-control constraint efficiently.

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 simple two-parameter destructive operation, the description plus schema and annotations cover the essential facts: what happens, which parameters are needed, and who is allowed to call it. It lacks edge-case details like owner self-removal or post-removal behavior, but these are not critical for basic tool selection and invocation.

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%, with both tripId and collaboratorUserId documented. The description adds no additional parameter-specific meaning beyond the owner restriction, so the baseline score of 3 is 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?

The description uses a specific verb ('remove') and resource ('collaborator from a trip'), making the operation clear. It does not explicitly distinguish itself from sibling tools like trip_share_revoke, but the collaborator framing separates it from list/share operations reasonably well.

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?

The 'owner only' qualifier gives a clear authorization context for when this tool can be invoked. However, it does not state when to prefer this over alternatives such as trip_collaborators_list or trip_share_revoke, nor does it describe what not to use it for.

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