netsuite_describe

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

The description discloses that results are limited to tables/columns visible to the configured NetSuite role, which is a role-based visibility behavior. However, it does not mention error behavior (e.g., if the table doesn't exist) or the exact return format, and there are no annotations to supplement.

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, efficient sentence that immediately identifies the tool's action and subject. No filler or redundancy.

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 simple single-parameter describe tool with no output schema, the description covers the core purpose and the role-scoping constraint. It could add what the returned columns include (e.g., types, names), but is otherwise sufficient.

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 description adds the 'exact' qualifier to the table parameter, indicating that the table name must match precisely. Given the schema has 0% description coverage, this is useful but minimal; it doesn't explain what constitutes a valid NetSuite table name.

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 'describes columns' for a specific table, and the qualifier 'one exact table' and 'visible to the configured NetSuite role' add specific scope. This distinguishes it from sibling tools like netsuite_tables (listing tables) and netsuite_query (querying data).

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 provides no guidance on when to use this tool versus alternatives. It simply states what it does without mentioning prerequisites, exclusions, or referring to sibling tools.

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