remove_vendor

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

The annotation already declares destructiveHint=true, so the agent knows it's destructive. The description adds no extra behavioral context (e.g., whether it permanently deletes or just unbooks, impact on associated data). The vague term 'unbook' could mislead about reversibility.

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 very short (3 words), which is concise but sacrifices important information. It could include context about the destructive action or return value. 'Unbook' is not standard terminology. It earns a borderline score.

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?

Given no output schema and only one parameter, the description should at least clarify the effect of the action (e.g., 'Permanently removes the vendor') and any side effects. The current description is too minimal to be fully informative for an AI agent.

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 schema already describes the uuid parameter as 'Vendor UUID from list_vendors', which is clear. The description adds no additional semantics beyond the schema, so baseline 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 'Unbook a vendor' combined with the tool name 'remove_vendor' and sibling tools like add_vendor and list_vendors makes the purpose clear: to remove a vendor from the vendor list. However, 'unbook' is slightly ambiguous and could imply cancellation rather than deletion, preventing a perfect score.

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 description provides no guidance on when to use this tool, prerequisites (e.g., vendor must exist via list_vendors), or when to avoid it (e.g., preferring update_vendor to deactivate). No alternatives are mentioned.

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