remove_vendor

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

The annotations already provide destructiveHint=true, and the description adds no behavioral context beyond that. It does not disclose what gets unbooked or destroyed, whether the action is reversible, or what side effects occur on related vendor data.

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 brief and front-loaded with no wasted words, but it is under-specified rather than appropriately concise. 'Unbook a vendor' is a complete sentence, but it leaves essential meaning about scope and effect to inference.

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 destructive operation with no output schema, this description is incomplete. An agent needs to know what 'unbook' means operationally, what is affected, and what the result looks like; none of that is provided.

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 the uuid parameter description already tells the agent to use a UUID from list_vendors. The tool description adds no further parameter meaning, so the baseline of 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?

The description states a specific resource ('vendor') and an action ('unbook'), so it is not a tautology. However, 'unbook' is ambiguous—it could mean deleting the vendor record or marking it as not booked—and the description does not differentiate this from the sibling add_vendor/update_vendor operations beyond the general direction.

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?

There is no guidance on when to use this tool versus alternatives such as update_vendor or remove_guest, and no context about preparation steps. The only implicit hint is the destructive annotation, which is not enough to help an agent decide between this and sibling tools.

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