wordpress_backup_files

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 only indicates this is a backup operation without specifying critical details like whether it's read-only or destructive, what permissions are required, how it handles existing backups, or if it triggers any side effects. This leaves significant gaps for a mutation tool.

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, efficient phrase that front-loads the core purpose ('Backup files only') with a clarifying exclusion ('no database'). Every word earns its place with no redundancy or wasted space.

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 insufficient. It lacks details on behavioral traits (e.g., safety, permissions), output format, or error handling. Given the complexity of backup operations, this leaves the agent under-informed.

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 no parameter documentation is needed. The description doesn't add parameter details, which is appropriate, but it could optionally mention implicit parameters like backup scope or format. Baseline is 4 for zero parameters.

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 action ('Backup') and resource ('files'), distinguishing it from database backups. However, it doesn't specify what types of files (e.g., WordPress core, themes, plugins, uploads) or the backup destination, which prevents a perfect score.

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 explicitly differentiates from 'wordpress_backup_database' by stating 'files only (no database)', providing clear context for when to use this tool versus its sibling. However, it doesn't mention alternatives like 'wordpress_full_backup' or 'wordpress_schedule_backups', which could be relevant.

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