sql_query

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

With no annotations, the description carries full burden. It mentions support for DDL (destructive) and DML (data modification) but fails to disclose potential side effects like table locking, long-running queries, or required permissions. This is insufficient for safe agent usage.

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, front-loaded sentence that efficiently states the purpose. It is concise, but additional critical information (e.g., output format) is missing, preventing a higher score.

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 nested objects, the description lacks output schema details and fails to inform the agent about what the tool returns (e.g., rows, affected count). Sibling tools hint at related functionality, but the description is too sparse for a generic SQL executor.

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 single parameter 'sql' is fully described in the input schema (100% coverage). The tool description does not add any additional semantics or constraints beyond the schema, so baseline score of 3 is appropriate.

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 'Execute SQL query' and specifies support for DDL and DML operations, which distinguishes it from read-only or log retrieval sibling tools. However, it could be more precise about the exact types of SQL statements allowed (e.g., SELECT, INSERT, etc.).

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 guidance is provided on when to use this tool vs. siblings like check_permissions or get_database_info. There is no mention of prerequisites, authorization, or context such as needing to validate permissions before execution.

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