netsuite_get_bill_payment

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

No annotations are provided, so the description must fully disclose behavior. It states the operation is 'Get' (read-only), which is also inherent in the tool name. It provides no additional context about error handling, permissions, side effects, or what happens if the ID does not exist. The description adds no value beyond what the name already conveys.

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 main purpose, and provides exactly the necessary information about the required parameter. Every word is informative, with no redundancy or 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?

The tool is simple (one parameter, no output schema), but the description omits what the tool returns (e.g., the full payment record) and any error behavior. It covers the core function and parameter adequately, but the absence of return-value specification and edge-case handling leaves it marginally incomplete.

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 has one parameter (id) with no description (0% coverage). The description compensates by explaining 'id (string, payment ID)', giving the parameter semantic meaning and confirming its type. This adds value beyond the bare schema definition.

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 verb 'Get' and the specific resource 'NetSuite vendor payment (bill payment)' with scope 'by ID', which distinguishes it from sibling tools like netsuite_get_bill_payments (plural). The purpose is 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 implies usage for fetching a single payment by ID, but it does not explicitly state when to use this tool versus alternatives such as listing all bill payments. No exclusions or alternative references are given, making the guidance implicit rather than explicit.

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