create_vendor

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

With no annotations, the description carries the full burden of behavioral disclosure, but it only repeats the fact that the tool creates a vendor. It does not explain side effects, required permissions, idempotency, validation behavior, or the passthrough to Bigcapital, leaving the agent without transparency into what happens when the tool is invoked.

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 extremely short and front-loaded, but it is under-specified rather than appropriately concise. It provides no more information than the tool name, so brevity comes at the cost of usefulness.

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 an opaque nested body parameter and no output schema, the single sentence does not tell an agent what fields the Bigcapital API expects, whether a vendor account is created immediately, or what success/error responses look like. The context is incomplete for correct invocation.

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%: the body parameter's description says it is 'passed through to Bigcapital', and additionalProperties allow arbitrary content. The main description adds no parameter semantics, but the schema is sufficiently explicit, 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 description 'Create a vendor.' is a direct restatement of the tool name, so it names the verb and resource but adds no new information that would help disambiguate it beyond the name. It does not mention the Bigcapital integration, how it differs from update_vendor or create_customer, or any specifics of what constitutes a vendor.

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?

No guidance is given for when to use this tool instead of update_vendor, get_vendor, or list_vendors, nor are any prerequisites or exclusion conditions mentioned. The only usage cue is the verb 'create', which is already present in the tool name.

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