mysql_list_constraints

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

No annotations are provided, so the description carries full responsibility. It correctly portrays a read-only, side-effect-free operation but omits potential constraints like required privileges (e.g., SELECT on information_schema). Basic disclosure is present.

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?

Single sentence with no wasted words. However, it could be slightly more informative without losing conciseness. Appropriately sized for a simple list tool.

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 straightforward listing tool, the description is minimal but functional. It lacks output schema info and parameter details, but no critical gaps for basic use. Could be improved with notes on required permissions or output structure.

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 only 33% (only connectionId has a description). The tool description does not elaborate on 'table' or 'database' parameters, leaving ambiguity about format (e.g., schema.table vs bare name). Without compensation, param semantics are weak.

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 action ('List') and the resource ('table constraints and foreign keys in a MySQL database'). It is specific and distinct from sibling tools like mysql_describe_table or mysql_list_indexes.

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 explicit guidance on when to use this tool versus alternatives (e.g., mysql_describe_table, mysql_show_create_table). Usage is implied by the name and sibling list, but no direct reasoning is provided.

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