database_dump

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

Describes write operation (creates root-owned file), file return details (path, size), and rejection of remote servers/non-MySQL. Adds context beyond annotations (SSH requirement, staging dir restriction) without contradicting readOnlyHint=false.

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?

All sentences are informative and necessary. Front-loaded with purpose, followed by constraints and usage steps. No redundancy.

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?

Covers prerequisites, output format, behavioral flags, and limitations. Without output schema, description adequately explains return values (path and byte size).

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 covers 2 of 4 params with descriptions; description adds usage context for dry_run/confirm (preview/execute) and clarifies output_path scope (staging dir only). Fully compensates for missing schema descriptions.

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?

Clearly states 'Dump a database to a .sql file' using specific verb and resource. Distinguishes from sibling tools like databases_list and database_import by specifying dump/export via SSH and mysqldump.

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?

Explicitly mentions prerequisites (SSH configured, staging dir), how to preview vs execute (dry_run, confirm), and constraints (local MySQL only, file path restrictions). Lacks direct comparison to alternatives but boundaries are clear.

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