netsuite_create_bill_payment

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

No annotations are provided, so the description carries the burden. It discloses key behaviors: auto-resolution of account, default currency, idempotence via externalId, and the unapplied payment caveat. However, it does not mention permission requirements, post-save effects, or response format, so it falls short of a 5.

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 concise and well-structured: the main action is front-loaded, followed by a clear breakdown of required and optional parameters, and a notable caveat. Every sentence is informative and no filler exists.

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 7-parameter tool with no annotations and no output schema, the description covers essential behavioral aspects (defaults, idempotence, unapplied payment). It lacks information on return values, error cases, and permission requirements, but is still substantially complete for a creation 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 0%, so the description must compensate. It does so excellently by explaining each parameter's purpose, format, optionality, defaults, and the structure of the 'apply' array. This adds significant meaning beyond the bare 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?

Description clearly states 'Create a NetSuite vendor payment (bill payment) and apply it to one or more vendor bills,' with a specific verb and resource. It distinguishes from siblings like create_vendor_bill and create_vendor_credit by specifying the payment context and application to bills.

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 when to use the tool (to create vendor payments) and provides clear parameter usage, but does not explicitly mention alternatives or exclusions. Since the context is clear and no misleading guidance exists, it earns a 4.

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