wordpress_backup_database

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

With no annotations provided, the description carries full burden. 'Export database only' suggests a read-only operation that creates an output file, but doesn't disclose critical behavioral traits: whether this requires admin permissions, what format the export uses (SQL dump, compressed file), where the export is saved, if it's destructive to existing data, or if there are rate limits. The description is insufficient for a tool that presumably creates database backups.

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?

Extremely concise at just three words with zero waste. The description is front-loaded with the essential action and scope. Every word earns its place by distinguishing this from file backups and full backups.

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 database export/backup tool with no annotations and no output schema, the description is incomplete. It doesn't explain what the tool actually produces (file format, location), what permissions are required, whether it affects site performance during export, or how to access the exported data. The agent would be left guessing about critical operational details.

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 tool has 0 parameters with 100% schema description coverage, so the baseline is 4. The description doesn't need to explain parameters, and 'Export database only' appropriately indicates this is a parameterless operation that performs a complete database export.

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 'Export database only' clearly indicates the action (export) and resource (database), but it's vague about the scope and format. It distinguishes from sibling 'wordpress_backup_files' and 'wordpress_full_backup' by specifying 'database only', but doesn't clarify if this is a backup operation or a data export for other purposes.

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 explicit guidance on when to use this tool versus alternatives like 'wordpress_backup_files' or 'wordpress_full_backup'. The description implies it's for database-specific operations, but doesn't state prerequisites, timing considerations, or when other backup tools might be more appropriate.

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