expense_add_vendor

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

No annotations are provided, so the description carries full responsibility for behavioral disclosure. While 'Add' implies a write/mutation operation, the description doesn't mention permission requirements, whether vendor creation is reversible, what happens on duplicate vendor IDs, or what the response contains. For a mutation tool with zero annotation coverage, this represents a significant gap in transparency.

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, efficient sentence that gets straight to the point with zero wasted words. It's appropriately sized for a basic tool description and front-loads the essential information.

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 mutation tool with 8 parameters (3 required), no annotations, no output schema, and 0% schema description coverage, the description is inadequate. It covers only the basic purpose while missing critical information about parameters, behavioral characteristics, return values, and usage context that an agent needs to effectively invoke this tool.

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?

With 0% schema description coverage for 8 parameters (3 required), the description provides no information about any parameters. It doesn't explain what vendorId represents, what contactInfo structure is expected, or the meaning of fields like taxId, paymentTerms, or preferredPaymentMethod. The description fails to compensate for the complete lack of schema documentation.

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 clearly states the action ('Add') and resource ('a new vendor to the system'), making the tool's purpose immediately understandable. However, it doesn't distinguish this tool from potential siblings like 'expense_add' or 'expense_vendor_analysis', which could be related operations in the expense domain.

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 versus alternatives, prerequisites, or any context for its application. With many sibling tools in the expense domain (e.g., expense_add, expense_vendor_analysis), this lack of differentiation leaves the agent guessing about appropriate use cases.

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