wordpress_full_backup

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

With no annotations, the description must disclose behavioral traits. It only states the action ('create backup') without detailing side effects (e.g., overwriting existing backups), required permissions, or whether the backup is synchronous. The agent is left unaware of important operational aspects.

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?

A single sentence that is front-loaded and contains no redundant information. Every word serves a purpose, making it highly efficient for the agent to parse.

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?

Given the complexity (backup operation) and absence of output schema, the description lacks details on return values or storage location. No annotations compensate. The simple description may be adequate for a zero-parameter tool but leaves ambiguity about what the agent receives after invocation.

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 parameters, so the description does not need to explain parameters. The baseline for zero parameters is 4, and the description adds value by clarifying the backup scope (files + database), which is not evident from the empty schema.

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 clearly states 'Create complete site backup (files + database)', specifying the verb and resource. It differentiates from sibling tools like wordpress_backup_database and wordpress_backup_files, which are partial backups, making the tool's distinct purpose evident.

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 the partial backup siblings. The distinction is implied by the names and description, but the description does not directly advise the agent on selection criteria or prerequisites.

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