netsuite_get_vendor_bills_for_vendor

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

With no annotations provided, the description carries the burden of behavioral disclosure. It does add useful details beyond the schema: the date format 'YYYY-MM-DD' and the default limit of 50. However, it does not disclose the return format (e.g., array of vendor bills) or any error/edge-case behavior, leaving some gaps.

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: a purpose statement followed by a compact parameter list. Every word is informative, with no fluff or redundancy. It is front-loaded with the action and resource.

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 or annotations, the description covers the essential aspects: purpose, required/optional params, and a default behavior (limit). It could be slightly more complete by explicitly stating the response shape, but the tool's simplicity makes this a minor gap.

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 zero descriptions for its parameters, so the description fully compensates by explaining each parameter: vendorId is required, from/to are dates in a specific format, and limit has a documented default. This is comprehensive parameter documentation over and above the bare schema.

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 a specific verb 'Get' plus a resource 'vendor bills' and narrows scope to 'for a specific vendor', clearly distinguishing it from sibling tools like netsuite_get_vendor_bills which likely returns all bills. The required vendorId parameter reinforces that this is a scoped lookup.

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 provides clear context that this tool is for retrieving bills of one vendor, and the optional date range gives additional filtering usage. However, it does not explicitly mention when not to use it or point to alternatives (e.g., netsuite_get_vendor_bills for all vendors), so it falls short of a 5.

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