execute_sql

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

With no annotations, the description carries full burden. It discloses that arbitrary SQL (SELECT, INSERT, UPDATE, DELETE, DDL) is allowed, multiple statements via ';', and that errors return JSON with 'error'. However, it does not explicitly warn about destructive potential, but the listed operations imply it.

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 with separate Args and Returns sections, though the formatting is slightly verbose. Every sentence adds value.

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 one required parameter, no annotations, and an output schema described in the description, the description covers purpose, parameter behavior, return format, and error handling completely.

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 description coverage is 0%, so the description must add meaning. It explains that the 'sql' parameter accepts arbitrary SQL, lists allowed operations, and notes that multiple statements can be separated by ';'. This fully compensates for the lack of schema documentation.

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 explicitly states 'Exécute une ou plusieurs requêtes SQL sur la base SQLite', which is a clear verb (execute) + resource (SQLite database) and differentiates from any sibling (none provided).

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 does not provide explicit when-to-use or when-not-to-use guidance, but the tool's purpose is straightforward and no siblings exist, so the implied usage is clear.

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