mysql_list_triggers

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

With no annotations, the description must disclose behavioral traits. It only says 'List triggers' without indicating whether it is read-only, what permissions are needed, or any side effects. The description fails to provide sufficient 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?

While the description is short, it is under-specified for a tool with two parameters. It does not convey important details about the scope of triggers listed or any filtering. True conciseness would include essential context without verbosity.

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 the absence of an output schema, descriptions of parameters, and annotations, the description leaves significant gaps. Users cannot anticipate the response format, whether the list is limited to a database, or how to handle multiple connections. The tool's complexity is not matched by the description.

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 input schema covers 50% of parameters with descriptions (only connectionId has one). The description adds no additional meaning to parameters; it does not explain the 'database' parameter or any constraints. For a low-coverage schema, the description should compensate but does not.

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 specific resource (triggers in MySQL database). It is specific enough to distinguish from general list tools, but does not differentiate from sibling tools like mysql_list_tables or mysql_list_views, which follow the same pattern.

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 is provided on when to use this tool versus alternatives (e.g., mysql_list_tables for tables). There is no indication of prerequisites (e.g., required permissions) or context for optimal use.

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