netsuite_get_vendor_bill

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

With no annotations provided, the description carries the burden of behavioral disclosure. It states 'Returns full bill details with expanded sub-resources (expense lines, items)', which tells the agent what to expect in the response. However, it does not address potential errors, auth requirements, or rate limits, making it only moderately transparent.

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 two sentences, front-loaded with the core purpose and followed by a clear parameter explanation. Every sentence adds value with no redundancy or fluff.

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 single-get tool with one parameter and no output schema, the description is sufficiently complete. It explains what is returned (full bill details with sub-resources) and what the parameter is. It could include error behavior or response format specifics, but those are not critical for this level of complexity.

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 input schema only defines 'id' as a string with no description. The description compensates by stating 'Required parameter: id (string, NetSuite internal vendor bill ID)', adding meaningful semantics about what the parameter represents. This goes beyond the schema's bare type information.

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 tool's function: 'Get a single NetSuite vendor bill by internal ID.' It uses a specific verb ('Get') and resource ('single NetSuite vendor bill') and scopes it by 'internal ID', which distinguishes it from sibling tools like netsuite_get_vendor_bills (plural) and netsuite_get_vendor_bill_by_external_id.

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: use this tool when you have the internal ID of a specific vendor bill and need full details. It implicitly differentiates from alternatives by emphasizing 'single' and 'by internal ID', though it does not explicitly name alternatives or state when not to use.

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