execute_sql

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

Since no annotations are provided, the description carries the full burden of behavioral disclosure. It mentions 'raw SQL or native database command', implying potential write operations and risks, but fails to explicitly state that commands can modify data, require admin privileges, or that results may vary by connection type. The output schema exists but is not referenced.

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 sentence of 11 words, making it very concise. It includes the essential elements (execute, raw SQL, named connection) without fluff. However, the brevity leaves out important contextual details that could be added without significant lengthening.

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's complexity (3 parameters, no annotations, 0% schema coverage, output schema present), the description is incomplete. It omits the role of 'params', fails to explain what 'native command' means, and does not address security or error behavior. The output schema exists but is not mentioned, so the agent cannot infer what will be returned.

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 compensate. It defines 'connection_name' and 'command' but provides no additional meaning beyond the schema fields. The 'params' parameter is an optional object described only as 'anyOf object or null', with no explanation of its role (e.g., parameterized queries). The description adds minimal value over 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 raw SQL or native database commands on a named connection. This distinguishes it from siblings like 'query_database' and 'describe_table' by emphasizing raw execution and the need for a named connection.

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 specify when to use this tool versus siblings like 'query_database' or 'list_tables'. It lacks guidance on prerequisites (e.g., connection setup, permissions) and when not to use it (e.g., for read-only queries or exploratory analysis).

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