mysql_list_routines

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

The description is minimal and does not disclose what information is returned (e.g., routine names, definitions, or metadata). It also does not state whether this operation is read-only or requires specific privileges. With no annotations, the description lacks sufficient 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 very concise, using a single sentence. It is front-loaded with the verb and resource. However, it could afford a bit more detail without being wasteful.

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 lack of output schema, the description should describe the return format (e.g., list of routine names, types). It does not. The tool's simplicity partially compensates, but overall completeness is low.

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 coverage is 50% (only connectionId has a description). The tool description does not add any meaning to the parameters beyond the schema. It does not indicate that 'database' is likely required, nor does it explain the connectionId usage.

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 resource (stored procedures and functions) and implies a specific MySQL database context. It differentiates from sibling tools that list tables, views, etc. However, it could be more explicit about the database scope.

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_show_create_routine, mysql_list_triggers). There is no mention of prerequisites or limitations.

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