netsuite_get_vendor_bills

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

With no annotations, the description carries the full burden. It provides some behavioral details like the status format example ('VendBill:A') and optional pagination, but it does not disclose return format, default pagination behavior, or any read-only assurances. The tool is a read operation, but the description does not explicitly state safety or lack of side effects.

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 extremely concise—one sentence plus a compact parameter list. It is front-loaded with the primary purpose, and every word adds value. No unnecessary fluff.

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, the description covers the essential purpose and parameters, but it lacks completeness given the many sibling tools and no output schema. It does not mention what the response contains, whether all bills are returned when no filters are applied, or how to choose this tool over vendor-specific variants. This is adequate but has clear gaps.

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 so by explaining all four parameters: limit and offset for pagination, q as a search query, and status with an example value. This adds meaningful context beyond the bare schema and covers all parameters, though not with exhaustive syntax details.

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 bills with optional search and pagination, using a specific verb and resource. However, it does not explicitly distinguish itself from sibling tools like netsuite_get_vendor_bills_for_vendor, so it lacks explicit sibling differentiation.

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?

No guidance is given on when to use this tool versus alternatives such as netsuite_get_vendor_bills_for_vendor or netsuite_get_vendor_bill. The description implies usage via 'optional search and pagination' but does not state exclusions or preferred contexts.

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