⚠️ DESTRUCTIVE: Execute data modification SQL (INSERT, UPDATE, DELETE). Supports parameterized queries. Returns affected row count.

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

The description labels the tool as DESTRUCTIVE and states returns affected row count. However, no annotations are provided, and the description does not disclose permissions required, irreversibility, or side effects beyond modification. Basic transparency but not comprehensive.

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 very concise, using a single sentence plus title with a warning emoji. It is efficient but could benefit from slight structuring (e.g., bullet points for params). No unnecessary information.

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 3 parameters, 0% schema coverage, no output schema, and no annotations, the description is incomplete. It only covers general purpose and return type, failing to explain parameter usage or behavioral details needed for safe invocation.

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 0%, so the description should compensate. It mentions 'Supports parameterized queries' for the params parameter, but does not explain the format or the database_name parameter. The affected row count is mentioned as return, but no output schema exists. Minimal added value beyond the schema itself.

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?

Tautological: description restates name/title.

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 mentions 'Supports parameterized queries' which implies use, but lacks explicit guidance on when to use this tool versus alternatives (e.g., when to use transactions or read queries). No prerequisites or exclusions are provided.

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