query

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

With no annotations, the description carries the burden of disclosing behavior. It does state the tool only accepts SELECT statements and returns query results, which implies a read-only nature. However, it does not mention potential side effects, error handling, or result formatting, leaving some ambiguity.

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 extremely concise, consisting of two short sentences that each convey useful information: the action (execute SELECT) and the purpose (read data). It is front-loaded and has no wasted words.

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?

The description is sufficient for a simple tool, but it does not clarify how 'query' differs from the sibling 'execute' tool, which could cause confusion. It also does not describe the return format or any limitations. Given the minimal schema and no output schema, more contextual detail would be helpful.

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%, and the parameter 'sql' is described as the SELECT query to execute. The tool description adds little beyond repeating 'SELECT', which is already in the schema. Thus, it meets the baseline but does not go beyond.

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 SELECT queries and is used for reading data. This specific verb+resource combination (execute SELECT, read) distinguishes it from write-oriented siblings like insert, update, and delete.

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 implies this tool should be used for read operations ('用于读取数据'), which is clear context. However, it does not explicitly exclude other usages or mention alternatives such as the generic 'execute' tool, so it falls short of full guidance.

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