netsuite_get_vendor_bill_by_external_id

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

With no annotations, the description carries the full burden. It discloses the return shape precisely, including a 'found' boolean and a bill object or null, which indicates not-found behavior. The verb 'Get' implies a read-only operation, and the idempotency framing adds context. It does miss potential error handling details, but for a simple getter, it is sufficiently 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 one concise sentence plus a return-shape annotation. It is front-loaded with the purpose, states the requirement, and specifies the output. Every word earns its place with no redundancy.

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 the tool's simplicity (one parameter, no output schema), the description provides the essential information: purpose, required parameter, and return structure. It does not include error handling or rate limits, but these are not critical for a basic read operation. The return shape is disclosed, making the behavior predictable.

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 description coverage is 0%, so the description must compensate. It does identify the single parameter 'externalId' and its requirement, but it largely restates the schema (type string, required). It adds minimal meaning beyond the parameter name, which is self-explanatory. The description does not elaborate on format or provenance, so it provides only baseline compensation.

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: 'Get a vendor bill by its externalId' with a specific identifier type. This distinguishes it from sibling tools like netsuite_get_vendor_bill (likely by internal ID) and netsuite_get_vendor_bills (list). The term 'idempotency helper' adds useful context about the intended use case.

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 phrase 'idempotency helper' implies when to use this tool (for idempotent checks by external ID), but it does not explicitly state when not to use it or name alternative tools. This is implied guidance rather than explicit direction, so it meets the 'implied usage' benchmark.

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