netsuite_get_vendor_forms

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

With no annotations, the description carries the burden of behavioral disclosure. It states that the tool returns form IDs and mentions their use case, implying a read-only operation. However, it does not detail the output format (e.g., array of strings) or potential edge cases (e.g., no vendors, no custom forms). This is a minor gap for a zero-parameter tool, so a middle score is appropriate.

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: the first states the action, the second provides the use case. Every sentence earns its place, and it is front-loaded with the primary purpose. No unnecessary details or repetition.

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 the tool's simplicity (zero parameters, no output schema, no annotations), the description is largely complete. It explains what the tool returns and when to use it. It could be slightly more thorough by mentioning prerequisites or output structure, but given the straightforward nature, it is close to fully sufficient.

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 tool has zero parameters, and the schema is empty with 100% coverage. Per the rubric, the baseline for zero parameters is 4. The description adds no parameter-specific information because none are needed. It appropriately focuses on the output and usage, so no deduction is warranted.

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's function: 'Get list of custom form IDs used by existing vendors.' It specifies the resource (custom form IDs) and the action (get list), and it distinguishes itself from sibling tools by tying the output to vendor creation. This is a specific verb+resource combination that is immediately understandable.

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 a clear usage scenario: 'Use this if vendor creation fails with 400 to discover the correct customForm ID.' This tells the agent when to invoke the tool, but it does not explicitly name alternatives or contrast with other tools. It gives a concrete trigger condition, which is more than adequate for a simple lookup tool.

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