db_mysql_query

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

No annotations provided, so description must disclose all behaviors. States 'read-only' but doesn't clarify what happens if write queries are attempted, connection management, authentication, rate limits, or error handling. Minimal disclosure.

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?

Very short but under-specified. Conciseness is not valuable when critical details are missing. Every word should earn its place; here, 'read-only' is useful but the rest is insufficient for a tool with 2 undocumented parameters.

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 no output schema, no parameter descriptions, and no annotations, the description should provide more context about return format, error behavior, and that it's for SELECT queries only. Incomplete for the tool's complexity.

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 description must explain parameters. Only says 'read-only MySQL query' without mentioning that 'query' is the SQL string or 'params' is for parameterized queries. Adds almost no 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?

Description clearly states it executes a read-only MySQL query, specifying verb, resource, and a key constraint. Distinguishes from siblings like db_mongodb_query and db_postgres_query due to 'MySQL' mention.

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?

No guidance on when to use vs alternatives like db_mysql_health, no prerequisites, no when-not-to-use advice. The '[SAFE]' prefix hints at read-only nature but doesn't provide explicit usage context.

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