ecp_mysql_database_sizes

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

With no annotations provided, the description must carry the behavioral disclosure burden. 'Get' indicates a read-only operation and 'in bytes' adds output detail, but the description does not mention return format, error behavior, or whether any access requirements exist. Still, for a simple no-parameter read tool, the core behavior is reasonably clear.

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, front-loaded sentence with no filler. Every word contributes meaningful information: the action, the target, and the unit of measure.

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-parameter read-only tool with no output schema, the description provides the essential context: it returns sizes in bytes for each MySQL database. It could further describe the exact return shape, but the low complexity of the tool keeps this from being a major gap.

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 is empty and the parameter count is 0, so there are no parameters to document. Per the baseline for zero-parameter tools, this is adequate; the description reinforces that no filtering is offered by saying 'each MySQL database.'

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 states a specific verb ('Get'), resource ('each MySQL database'), and unit ('bytes'), which clearly defines what the tool does. It is immediately distinguishable from sibling tools like ecp_mysql_table_sizes and ecp_mysql_list_databases by scope and output.

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?

The description implies when to use the tool: whenever you need the size of each MySQL database. However, it does not explicitly contrast it with alternatives such as ecp_mysql_table_sizes or note when not to use it, so usage context is only implied rather than explicit.

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