sqlquery_execute

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

The description states it is a SELECT-only query and subject to permission control, which implies it is read-only and access-restricted. However, with no annotations provided, it does not disclose other behavioral traits like error handling, whether data is returned, or potential side effects, leaving 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?

The description is concise: a one-sentence purpose followed by a parameter list. It is front-loaded with the essential verb and constraint. Every sentence is necessary, though the parameter section could be more 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?

Given the tool executes SQL queries (a potentially powerful action) and has no output schema, the description fails to explain return values, error behavior, or how results are presented. It is incomplete for safe and effective use.

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?

With 0% schema description coverage, the description adds basic meaning by listing parameters with Chinese labels (e.g., '实例名称', '数据库名'). This helps map parameter names to their purpose but lacks detailed constraints, formats, or examples, providing only minimal added value beyond the schema.

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 executes SQL queries and explicitly restricts to SELECT only, which clarifies its scope. However, it does not explicitly differentiate from sibling tools like sql_check or sqlquery_describe_table, so it lacks explicit sibling differentiation.

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 only mentions permissions and SELECT-only constraint but does not reference sibling tools or scenarios for using sql_check instead.

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