netsuite_list_files

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

With no annotations provided, the description carries the full burden for behavioral disclosure. It does indicate that this is a read operation ('List') and mentions pagination support, which is useful. However, it does not disclose details such as default pagination behavior, response format, or whether permissions are required. This is a basic level of transparency, not rich context.

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-loaded with the primary purpose. It avoids unnecessary details and every word earns its place. This is an efficient and well-structured description.

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?

The tool is simple (a list operation with optional pagination), but with no output schema or annotations, the description should cover more. It covers the purpose and parameters adequately but does not describe the return value or any edge cases. Given the simplicity, it is sufficient but not thorough.

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 is empty, providing no parameter definitions. The description compensates by explicitly naming optional parameters 'limit (number)' and 'offset (number)', which clarifies the pagination semantics. This adds meaningful information that is missing from the schema, going beyond the baseline for high schema coverage.

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 'List files from NetSuite File Cabinet', with a specific verb ('List') and resource ('files from NetSuite File Cabinet'). This distinguishes it from sibling tools like netsuite_upload_file and netsuite_attach_file_to_record, which involve uploading or attaching files rather than listing. No ambiguity about the core function.

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 mentions 'optional pagination' and optional parameters 'limit' and 'offset', which give some hint about controlling result size. However, it provides no explicit guidance on when to use this tool versus alternatives, nor any exclusions or prerequisites. This is minimal guidance at best.

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