netsuite_update_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. It only says 'Update' which is already in the tool name, and does not reveal whether the update is partial or full, whether it returns the updated vendor, requires special permissions, or has any side effects. For a mutation tool, this is a significant gap.

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 concise sentence that conveys the action and the key parameter requirements. No wasted words; it is efficient and directly addresses the core purpose.

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 simple update tool with only four string parameters and no output schema, the description gives the essential action and parameter list. However, it omits what the tool returns (e.g., updated vendor object, success/failure) and any prerequisites. Given the low complexity, this is acceptable but not complete.

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?

The schema description coverage is 0%, so the description must compensate. It lists the parameter names and marks 'id' as required and others optional, but it does not explain the meaning or expected format of parameters like 'externalId'. The information provided adds minimal value over the schema's property names and required array.

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 ('Update an existing NetSuite vendor') with a specific verb and resource. It distinguishes itself from sibling tools like netsuite_create_vendor (create) and netsuite_get_vendor_by_id (get), leaving no ambiguity about its purpose.

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 implies the tool is for modifying existing vendors, but it does not explicitly state when to use it versus alternatives (e.g., create_vendor for new vendors, get_vendor_* for reading). No exclusions or alternative tool recommendations are provided, leaving the usage context only implied by the verb.

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