wordpress_backup_database

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

With no annotations provided, the description carries the full burden. It states the operation ('export database') but does not disclose any side effects, return format, output location, or prerequisites. The behavior is only minimally described, leaving the agent uncertain about what happens after invocation.

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 unnecessary words. It efficiently conveys the core function and scope, making it easy for an agent to parse quickly.

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?

The tool is simple (zero parameters), but the description lacks information about the export output, such as file format, location, or return value. Sibling tools like wordpress_list_backups provide some implicit context, but the description itself is not fully complete for predicting the outcome of a call.

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 has zero properties, so the baseline is 4. The description adds meaning to the empty schema by specifying that the database is exported, which is the essential semantic context. No parameter documentation is needed.

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 states a specific verb (export) and resource (database), and the word 'only' directly distinguishes it from sibling tools like wordpress_full_backup and wordpress_backup_files. This makes the tool's purpose unmistakable.

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 usage guidance is provided. The description does not explicitly state when to use this tool over alternatives, nor does it mention any prerequisites or exclusions. The 'only' suffix hints at a narrow scope but lacks direct comparison with other backup tools.

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