cpanel_mysql_list

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

With no annotations available, the description must convey behavioral traits. It only states that the tool lists databases and users, implying a read operation, but fails to disclose permissions needed, scope limitations, or error handling. No output schema or additional behavioral details are provided.

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, concise sentence that front-loads the purpose. It is efficiently written with no unnecessary words, though it could be slightly expanded to cover parameter details.

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 list tool, the description minimally covers functionality but omits parameter details for 'cpanel_user', usage context, and output format. Given the lack of output schema and annotations, the description is incomplete for an agent to use correctly without additional inference.

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 50% (only 'account' has a description). The tool description does not clarify the 'cpanel_user' parameter or provide any additional semantics beyond the schema. Baseline compensation for low schema coverage is expected but missing.

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'), the resource ('MySQL databases and users'), and the scope ('for a cPanel account'). It is a specific verb+resource combination that effectively differentiates it from sibling tools like whm_mysql_list_dbs.

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 such as whm_mysql_list_dbs or other listing tools. The description lacks context about prerequisites or typical use cases.

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