add_vendor

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

Annotations declare destructiveHint=false and openWorldHint=true, so the safety profile is partly covered. However, the description adds no behavioral context of its own: it does not say whether the vendor is persisted immediately, whether it is associated with the current wedding/event, or what reference_vendor_id does.

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 words with no filler, so nothing is wasted, but the sentence is under-specified rather than efficient. The core intent is front-loaded, which is the only structural merit.

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 9-parameter mutation tool with no output schema, the description should at minimum clarify creation semantics, required vs optional data, and any side effects. Annotations cover part of the safety story, but the description itself leaves a large gap.

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 all 9 parameters are already documented, including the vendor_type enum values and the ISO 8601 event_date note. The description contributes no additional parameter meaning, so the 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?

The phrase names a resource (vendor) and a creation intent, so an agent can guess this creates a vendor record. But the verb 'Book' is loose and at odds with the schema's plain create semantics (vendor_type, name, city, state_province), and it does not differentiate this tool from update_vendor, remove_vendor, or search_vendors.

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 when-to-use guidance, no prerequisites, and no mention of alternatives such as search_vendors for finding an existing vendor or update_vendor for changing one. Only the word 'new' hints at the create use case.

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