wordpress_delete_backup

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It does not state that the deletion is permanent, whether authentication is required, or if there are side effects on other operations (e.g., scheduled backups). The agent has no safety information.

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 concise at one short sentence, but at the expense of valuable information. Every word earned its place, but the description is under-specified for the required task.

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 simple single-parameter tool, the description should at least explain the parameter and expected outcome. It misses return value, error cases, and how to obtain the backupId. Sibling tools like wordpress_list_backups provide context but are not referenced.

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 coverage is 0%, and the description does not explain the parameter 'backupId'. The agent cannot infer what value to provide, its source (e.g., from wordpress_list_backups), or its format. The description adds no meaning beyond the 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?

Description 'Delete a backup file' clearly states the action (delete) and the resource (backup file). It distinguishes from general file deletion tools like wordpress_delete_file by specifying 'backup file'. However, it could be more specific about the scope of backups (e.g., WordPress backup system).

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 guidance on when to use this tool versus alternatives like wordpress_delete_file or wordpress_restore_backup. The agent is left to infer context from the tool name alone. There is no mention of prerequisites (e.g., backup must exist) or when deletion is appropriate.

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