netsuite_get_bill_payments

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

No annotations are provided, so the description must disclose behavior. It only says 'List' and mentions optional search/pagination, but does not explain authentication, rate limits, return format, or pagination details. This is a thin disclosure for a network operation.

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 single concise sentence plus parameter list, with no wasted words. It is front-loaded with the main action, though it could be structured more clearly for parameter details.

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?

With no annotations and no output schema, the description leaves gaps about what is returned, how pagination works, and what the search query searches across. For a simple list tool, it is minimally adequate but not complete.

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 0% description coverage, so the description adds some meaning by labeling parameters: limit (number), offset (number), q (string, search query). It connects limit/offset to pagination and q to search, which is helpful but does not explain the search syntax or default values.

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 lists NetSuite vendor payments (bill payments) and mentions optional search and pagination. It uses a specific verb ('List') and resource, distinguishing it from the singular 'get_bill_payment' sibling.

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 this tool is for listing multiple bill payments, but it does not explicitly compare with alternatives like 'netsuite_get_bill_payment' for single records. No exclusions or when-to-use guidance beyond the mention of optional search and pagination.

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