wordpress_full_backup

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

No annotations are provided, so the description must disclose behavioral traits. It only states that it creates a backup without mentioning where the backup is stored, how long it takes, potential performance impacts, or how to retrieve the backup. This is a significant gap for a mutation-like operation with no safety annotations.

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, concise sentence that is front-loaded with the action and scope. Every word earns its place, providing maximum clarity without waste.

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 backup tool with no annotations and no output schema, the description is too sparse. It doesn't explain the backup destination, return value, or follow-up actions (e.g., using wordpress_list_backups to retrieve it). The description covers the 'what' but not the 'what happens next' or operational impact, making it incomplete for an agent to use effectively.

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 zero parameters, so schema coverage is 100% trivially. Per the rubric, 0 params warrant a baseline of 4. The description adds no parameter information because none 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 clearly states the tool's function: 'Create complete site backup (files + database)'. The verb 'Create' and resource 'backup' are explicit, and the parenthetical 'files + database' distinguishes it from sibling tools like wordpress_backup_database and wordpress_backup_files, which are partial backups.

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 provides clear context: this tool is for a complete backup including both files and database. While it doesn't explicitly name alternatives or exclusions, the phrase 'complete site backup' implies it is used when a full backup is needed, as opposed to partial backup tools. This is sufficient for a 4, but lacks explicit when-not-to-use guidance.

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