netsuite_query

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

The description discloses 'read-only' and 'bounded', which are important safety traits, especially given no annotations are provided. However, it does not elaborate on what 'bounded' entails (e.g., row limits, timeout behavior) or the format of results, leaving gaps in behavioral understanding.

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 a single, front-loaded sentence with no redundant words. It efficiently conveys the core action and key constraints, making it highly concise and well-structured.

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 tool that executes arbitrary SQL, the description lacks crucial details such as output format, error handling, and specific limit behavior. The vague term 'bounded' and absence of an output schema make the description insufficient for fully understanding the tool's behavior.

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 provides no descriptions, and the tool description only hints at 'bounded' without explaining max_rows or timeout_seconds. It also does not clarify the meaning of the sql parameter, so the description adds minimal value to parameter understanding.

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 it executes a SuiteAnalytics Connect SQL query, with specific qualifiers 'bounded' and 'read-only'. This distinguishes it from sibling tools like netsuite_tables or netsuite_describe, which serve different purposes.

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?

There is no guidance on when to use this tool versus alternatives. The description does not mention conditions under which one should choose a different tool, such as when listing tables or describing metadata, leaving the selection entirely to inference.

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