netsuite_create_vendor_bill

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

With no annotations, the description carries the burden of behavioral disclosure. It adds useful context such as 'Set department from cost center map for analytics' and the critical note that vatLines sets taxDetailsOverride so the tax authority ledger is updated. However, it omits permissions, response shape, dryRun behavior, and error conditions.

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 compact two-sentence block, front-loaded with the primary purpose, then systematically listing required/optional fields and specific guidance. It is dense but efficient, with no filler.

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?

Given 15 parameters and no annotations or output schema, the description covers required fields, expense line structure, and VAT handling well. However, it leaves gaps around return value, dryRun behavior, externalId semantics, and potential errors, making it substantial but not fully complete for a complex create 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?

Schema coverage is only 47%, but the description compensates by explaining the expense array structure ('array of lines with account, amount as NET, memo, department, location, class, taxCode'), clarifying required fields and date format (YYYY-MM-DD), and describing VAT line semantics. This adds significant meaning beyond the sparse schema.

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 'Create a new NetSuite vendor bill with expense lines' and lists required fields, distinguishing it from sibling tools like create_vendor_credit or update_vendor_bill. The verb and resource are specific and unambiguous.

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 clear context for use by listing required and optional fields, advising to set department from the cost center map, and explaining when to use vatLines for VAT. It does not explicitly name alternatives or exclusions, but the usage context is well implied.

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