ecp_mysql_export_database

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It reveals that the output is returned as text and warns that large databases produce large results, which is a meaningful behavioral caveat. It does not mention permissions or side effects, but 'export' and the stated text-return behavior cover the main operational expectations.

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 sentence that front-loads the core action and return format, then immediately adds the large-result warning and alternative tool. Every clause earns its place with no redundant filler.

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 one-parameter tool with no output schema, this is complete enough: it states the action, the return format, the operational caveat about size, and the appropriate fallback. An agent can decide whether to call it or use the storage backup sibling without needing additional context.

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 describes db_name only as a string with no explanation, and the description adds no parameter-level detail beyond the general 'MySQL database' phrase. With 0% schema description coverage, the description should compensate by explaining what db_name expects, but it does not.

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 and resource: 'Export a MySQL database as a .sql dump'. It also names the key differentiator from the sibling backup tool by noting the dump is 'returned as text', making it easy to distinguish from ecp_mysql_backup_to_storage_bd.

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 gives explicit when-to-use guidance: use this tool for a quick look, but consider ecp_mysql_backup_to_storage_bd for anything beyond that. This clearly routes the agent to the correct sibling based on size and intent.

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