List MySQL databases

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is fully covered. The description adds only the returned fields (size, assigned users), which is useful given there is no output schema, but says nothing about pagination behavior, permission requirements, or empty-account results.

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?

One sentence, front-loaded with the action and resource, with the value-add (size and users) trailing. Nothing redundant and nothing padded.

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 paginated read with a fully documented three-parameter schema and complete annotations, the description covers purpose and return content adequately. A note on what an empty result means or on account-existence errors would close the remaining gap, but no output schema is expected here.

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 100%, with 'user' even cross-referencing whm_list_domains and 'offset' explaining next_offset usage. The description adds no parameter meaning beyond the schema, so the baseline 3 applies.

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 names a specific verb and resource ('List an account's MySQL databases') and adds the scope of returned data ('with their size and assigned users'). It is clearly distinct from siblings like whm_disk_usage or whm_get_account, though it never explicitly contrasts with the adjacent whm_list_database_users.

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?

It implies per-account scope via 'an account's' but gives no explicit when-to-use guidance, no prerequisites, and no named alternative. An agent must infer from the sibling list that whm_list_database_users is the complement, not a substitute.

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