netsuite_get_vendor_credits

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

No annotations are provided, so the description must disclose behavioral traits. It mentions optional search and pagination but does not confirm read-only status, describe default/max pagination limits, specify q field semantics, or outline return format. The agent is left to infer behavior from the tool name.

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 primary action, and includes a concise parameter list. Every sentence adds value with no filler, making it appropriately sized and well-structured.

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 three optional parameters and no output schema or annotations, the description covers basic semantics but lacks context on pagination behavior, searchable fields, and expected response shape. It is adequate for a simple list tool but incomplete for an agent needing to handle edge cases.

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 adds 'search query' semantics for q and marks all parameters optional, but limit and offset only receive their type names without defaults or range info. This provides some meaning beyond the bare schema but not comprehensive.

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 uses 'List' as a specific verb with 'NetSuite vendor credits' as the resource, clearly indicating a list operation. It distinguishes from sibling tools like netsuite_get_vendor_credit_by_external_id (single record) and netsuite_create_vendor_credit (write operation).

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 bulk listing or searching via 'List' and 'optional search', but it does not explicitly name alternatives or state when not to use this tool. Sibling names provide contrast, but no explicit exclusion or alternative guidance is given.

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