netsuite_get_expense_reports

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

No annotations are present, so the description must disclose behavioral traits itself. It mentions optional search and pagination and gives a status example, but it does not describe default pagination behavior, what fields q searches, or the response shape. This leaves significant ambiguity for a read tool with no annotation safety net.

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 with the primary action front-loaded. Every phrase contributes value; no filler.

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 description covers the list action and all parameters, but omits return value details and any default or boundary behavior. Given no output schema and no annotations, it is functional but incomplete for selecting confidently.

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 coverage is 0%, so the description must compensate. It defines q as a search query, status with a concrete example, and notes limit/offset for pagination. This adds meaning beyond raw property names, though limit/offset semantics are only implied.

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 expense reports with optional search and pagination. The verb 'List' distinguishes it from single-record siblings like get_expense_report_by_id and get_expense_report_by_external_id, and the mention of search/pagination frames it as a query tool.

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 for listing/filtering, but does not explicitly contrast with sibling tools for fetching individual reports. No when-not-to-use guidance is provided, so the agent must infer the distinction from the tool name and context.

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