netsuite_get_classifications

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 mentions optional limit and offset parameters, implying pagination, and the verb 'List' suggests a read operation. However, it does not state whether the operation is read-only, what the response format looks like, or any constraints such as default limits or required authentication. This is adequate for a simple list but lacks depth.

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 concise sentences, front-loading the core purpose and then noting the optional parameters. No redundant or filler content. Every sentence adds value.

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?

Given the lack of annotations and output schema, the description does its best to cover purpose and pagination, but it omits return structure, default pagination behavior, and any prerequisites. For a simple list tool this may be sufficient, but it could be more complete, especially since the schema is empty and no output schema exists.

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 input schema defines no properties, yet the description mentions optional 'limit' and 'offset' parameters with types. This adds meaning beyond the schema, but it also creates a contradiction with the schema's empty properties. The description does not explain what limit and offset control (e.g., page size, starting position), leaving some semantic ambiguity.

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 action ('List NetSuite classifications') and resource, with a brief clarification of what classifications are (analytical dimension for project/product/business unit tracking). This verb+resource structure is unambiguous and distinguishes it from sibling list tools for other NetSuite entities.

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: use this tool when you need to list classifications. However, it does not provide explicit guidance on when to choose this over alternatives, mention any exclusions, or suggest sibling tools. The purpose is clear enough that the intended use is obvious, but there is no direct comparison to other listing tools.

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