query_database

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

With no annotations, the description carries full burden but only says 'Execute a SQL query', which could imply either read or write operations. It fails to disclose important behaviors like mutation potential, error handling, or query limits, leaving the agent without critical safety context.

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 concise sentence that communicates the core purpose without any extraneous information. It is efficiently front-loaded and earns its place.

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?

Despite having only one parameter and no output schema, the description omits crucial context such as return format (rows, error messages) and whether queries can be read-only or mutating. This leaves the agent with insufficient information to predict behavior.

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%, so the parameter 'sql' is fully described in the schema. The tool description adds no extra meaning beyond 'Execute a SQL query', not specifying syntax details or constraints. This meets the baseline for high schema coverage but provides no added value.

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') and the resource ('SQL query on the local MySQL database'), making the tool's purpose unambiguous. It is distinct from sibling tools like get_container_logs, which are unrelated to database queries.

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 tool's purpose is clear, and there are no overlapping sibling tools, so an agent can easily infer when to use it. However, the description lacks explicit guidance on when not to use it or alternatives (e.g., for read-only queries vs modifications).

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