db_exec

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

No annotations provided. Description only states 'mutating', implying writes, but lacks details on side effects, permissions, or destructiveness. Minimal disclosure beyond the tool's basic nature.

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 short (6 words) and front-loaded. While concise, it sacrifices necessary detail; it is minimally adequate but could include parameter guidance without excessive length.

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?

No output schema, no annotations, and 0% schema coverage. The description fails to elaborate on SQL execution context, alias meaning, parameter usage, or return value. Incomplete for a 3-parameter mutation tool.

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%. The description adds no meaning to parameters (alias, sql, params). It does not explain their purpose or format, leaving the agent to infer from names.

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 'Run a mutating SQL statement (INSERT/UPDATE/DELETE)', clearly identifying the verb and resource. It distinguishes from sibling tool db_query by specifying mutating operations.

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 use for INSERT/UPDATE/DELETE but does not explicitly mention when not to use or name alternatives like db_query for SELECT. Context is clear but lacks guidance on exclusions.

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