ecp_mysql_list_databases

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

No annotations are provided, so the description carries the full behavioral burden. It implies a read-only enumeration by using 'List', but it does not disclose details such as whether it returns database names, placeholder handling, potential throttling, or any hidden side effects. This is minimal but adequate for a simple listing action.

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, unambiguous sentence with no filler or redundancy. It is front-loaded with the verb and object, and every word earns its place.

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 zero-param list action, the description is mostly complete knowledge of the tool's purpose. However, with no output schema, it leaves an agent to guess whether the result is a simple name list, includes metadata/sizes, or appears in a particular format. These are modest but concrete contextual gaps.

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 tool has zero parameters, so the baseline is 4. The description adds conceptual scope by mentioning 'this account's MySQL databases', which helps an agent understand the exact resource being listed even though no input schema is needed.

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 uses a specific verb+resource combination: 'List this account's MySQL databases.' It clearly communicates the tool's function and the account-level scope, which differentiates it from sibling tools for Mongo, MSSQL, Postgres, and related MySQL actions.

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 given about when to choose this tool over alternatives, what prerequisites exist (e.g., requiring a database server/remote to be available), or when not to use it. An agent must infer usage purely from the name and the simple description.

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