mysql_query

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

No annotations are provided, so the description carries the full burden. It discloses the read-only nature, which is crucial for safe usage, but does not mention potential side effects (e.g., locks, resource consumption) or details about connection handling or query result size limits.

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 contains no redundant words. Every word contributes to defining the tool's core function, making it easy to parse quickly.

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 two parameters with full schema documentation and no output schema, the description is adequate but leaves gaps. It does not hint at return format (e.g., rows as JSON) or mention validation of the sql parameter. For a simple read-only tool, it is moderately complete.

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 100%, so the schema already documents both parameters. The description adds no additional meaning beyond what the schema provides (e.g., format constraints, examples, or edge-case behaviors). Baseline 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 the verb 'Run', the resource 'a read-only SELECT/SHOW/EXPLAIN query', and the context 'against a configured MySQL connection'. It specifies allowed query types (SELECT, SHOW, EXPLAIN) and emphasizes read-only, which distinguishes it from write-oriented sibling tools like mysql_execute_sql.

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 read-only usage by listing allowed statement types, but it does not explicitly say when to use this tool versus alternatives or provide when-not-to-use guidance. No alternative tool names are mentioned, though the sibling list includes mysql_execute_sql for writes.

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