List MySQL databases

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

With no annotations provided, the description carries the burden of disclosing behavior. It adds context by noting the 'read-only' user and visibility scope, but does not describe return format, pattern filtering effects, or error behavior. This is some, but not rich, behavioral transparency.

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 with no unnecessary words. Every word contributes to conveying the tool's purpose and access scope.

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?

For a simple read-only listing operation with one optional parameter, the description provides sufficient context (action, resource, scope). The schema covers the parameter, and the absence of an output schema is mitigated by the obvious return type implied by 'List'. Could be slightly more detailed, but adequate for this low 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?

The single optional parameter 'pattern' is fully described in the schema as 'Optional MySQL LIKE pattern.' The tool description adds no additional meaning beyond this, so the baseline score of 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 tool's action ('List') and resource ('databases'), with a specific scope ('visible to the configured read-only MySQL user'). It distinguishes from sibling tools like mysql_list_tables and mysql_query, which target different resources or 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 usage for enumerating databases but does not explicitly state when to prefer this over alternatives like mysql_query or mysql_list_tables. It also lacks mention of prerequisites or exclusions, though the 'read-only' phrasing hints at safe usage.

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