ncloud_dataquery_execute

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

No annotations are provided, so the description should disclose behavioral traits. It mentions synchronous execution and pagination support but lacks details on side effects (e.g., does it support INSERT/UPDATE?), authentication needs, rate limits, or result format. For a query execution tool, these are significant gaps.

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?

Two concise sentences that front-load the action and service. No unnecessary words. Efficiently communicates the core functionality.

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?

Lacks information about return values, pagination mechanics, and supported SQL features. No output schema exists, so the description should compensate. The phrase 'pagination support' is vague and does not explain how to paginate. Incomplete for a tool with 8 parameters and no output schema.

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 100% with descriptions for all 8 parameters. The tool description adds no additional meaning beyond the schema (e.g., no explanation of how to use 'executionParameters' for parameterized queries). Baseline 3 is appropriate since high schema coverage reduces the need for extra param info.

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 action ('Execute a SQL query synchronously'), the service ('Ncloud Data Query (Trino-based serverless query service)'), and key behavior ('Returns results directly with pagination support'). It distinguishes from async siblings by specifying 'synchronously'.

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 explicit guidance on when to use this tool versus its async counterpart or other related tools. The description does not mention prerequisites, limitations, or scenarios where alternatives are preferred. The only implicit hint is the word 'synchronously'.

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