netsuite_get_vendors

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

With no annotations provided, the description carries the transparency burden. It discloses the use of SuiteQL for searches and the optional parameters, but does not state read-only status, return format, or pagination defaults. It adds some behavioral context but not comprehensive detail.

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 purpose, and every sentence adds value. It wastes no words and covers the essential aspect in a structured manner.

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 list tool with no output schema and 3 optional parameters, the description covers purpose and all parameters clearly. It lacks explicit return value details and pagination behavior, but is adequate for basic use.

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 itself has no parameter descriptions (0% coverage), but the description compensates by explaining each parameter: limit (number), offset (number), and q (search query on companyName via SuiteQL). It provides semantics beyond the raw schema, though it lacks constraints or examples.

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 ('List NetSuite vendors (suppliers)') and differentiates from siblings like netsuite_get_vendor_by_id or netsuite_get_latest_vendors by explicitly mentioning optional search and pagination. It is specific about the resource and scope.

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 conveys clear usage context: use this to list vendors, with optional filtering and pagination. However, it does not explicitly name alternatives or state when not to use it, so it falls short of fully comparative guidance.

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