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

Annotations already declare destructiveHint=true and openWorldHint=false, so the safety sentences are partly redundant. However the description adds genuinely new behavior: cascading deletion of activity, lodging and transportation assignments, plus the uncertain side effect of revoking pending invitations, which the agent cannot infer from annotations or schema.

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?

Three short blocks in a sensible order: action and consequences, parameter sourcing, then safety traits. No filler, and the irreversible effects are front-loaded where an agent scanning the definition will see them.

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?

With an output schema present, return values need no explanation, and both parameters are fully documented. What remains thin is permission/ownership requirements and whether removal is reversible, which would matter for a destructive collaborator operation.

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% and both parameters are already documented, including the warning that user_id is not a favorite or invitation id. The description only restates the source tool for user_id and adds nothing about trip_id, so baseline 3 applies.

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 ("Remove a guest from a trip") and immediately lists the effects: access revoked, assignments cleared. This is clearly distinct from siblings like tripsy_collaborators_invite and tripsy_collaborators_update, so an agent can route correctly without opening the schema.

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?

"Use the user id from collaborators" tells the agent where to source the required identifier, effectively pointing at tripsy_collaborators_list as a prerequisite. It does not state when removal is inappropriate or what to do if the guest owns data, so there is no explicit exclusion guidance.

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