mysql_query

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the tool is 'read-only', which implies non-destructive behavior and safety for data retrieval. However, it lacks details on authentication needs, rate limits, error handling, or response format, leaving gaps in behavioral context.

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, efficient sentence that front-loads the key information ('Run a read-only SELECT query') without any wasted words. It is appropriately sized for the tool's complexity and structure.

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 annotations and no output schema, the description is incomplete for a database query tool. It covers the basic purpose and read-only nature but lacks details on return values, error conditions, or operational constraints, which are important for effective tool use.

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?

The schema description coverage is 100%, so the schema already documents both parameters ('database' and 'sql') adequately. The description adds minimal value by reinforcing that the 'sql' parameter must be a 'SELECT query (read-only)', but does not provide additional syntax or format details beyond what the schema specifies.

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 specific action ('Run a read-only SELECT query') and the resource ('on a MySQL database'). It distinguishes this as a read-only query execution tool with no siblings to differentiate from, making the purpose explicit and complete.

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 usage by specifying 'read-only SELECT query', which suggests it should be used for data retrieval rather than modifications. However, it does not provide explicit guidance on when to use this tool versus alternatives (e.g., for write operations or other database types), as there are no sibling tools mentioned.

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