add_vendor

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

Annotations only include destructiveHint=false, so the description carries most of the burden. 'Book a new vendor' indicates a creation side effect but says nothing about persistence, idempotency, required permissions, response behavior, or whether reference_vendor_id must come from a prior search.

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 a single short sentence with no wasted words and is immediately understandable. It is concise, though extremely minimal for a tool with nine parameters.

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 creation tool with nine parameters, no output schema, and minimal annotations, this description is underspecified. It lacks guidance on when to use it, what the expected outcome is, and how the parameters relate to a real booking workflow.

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%, so the schema already documents all nine parameters. The description adds no additional meaning about parameter relationships, required fields, or how vendor_type should be chosen.

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 'Book a new vendor' uses a clear verb and resource, and the word 'new' signals a create operation. It does not explicitly distinguish itself from related tools like update_vendor or search_vendors, though the intent is inferable.

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 word 'new' implies this tool is for creating a vendor rather than updating or removing one. However, no explicit guidance is given about when to prefer this over search_vendors or update_vendor, and no prerequisites or exclusions are mentioned.

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