netsuite_tables

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

With no annotations, the description carries the full burden of behavioral disclosure. It does add the context of role-based visibility ('visible to the configured NetSuite role'), which is valuable, but it omits other critical behaviors such as read-only nature, search syntax, and result handling. The term 'bounded' is also unexplained.

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 wasted words. It is concise and easy to parse. However, the unclear term 'bounded' slightly reduces clarity, preventing a perfect score.

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 with no output schema and no annotations, the description is not complete enough. It fails to explain the semantics of the search parameter, the meaning of 'bounded', or the return format. The context provided is minimal, leaving the agent to guess critical operational details.

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 description coverage is 0%, and the description does not compensate. Neither 'search' nor 'max_results' is explained in relation to the tool's behavior. The agent receives no information about what constitutes a valid search or how the limit applies.

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 'Search bounded ODBC metadata visible to the configured NetSuite role' clearly identifies the tool's action (search) and resource (ODBC metadata), and distinguishes it from siblings like netsuite_query and netsuite_describe. However, 'bounded' is vague and the name 'tables' is not explicitly reflected, leaving some ambiguity about the exact scope.

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?

No guidance is provided on when to use this tool versus alternatives. The description simply states what it does without mentioning when it is appropriate or when another tool like netsuite_describe would be better. No exclusions or conditional context are given.

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