wordpress_backup_files

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

No annotations are provided, so the description must disclose behavioral traits. While 'backup files only' is clear, it doesn't explain the backup outcome (e.g., creates archive, where it's stored), any permissions or side effects, or return behavior. This is insufficient for an action that affects the file system.

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 extremely concise (5 words) and front-loaded, saying exactly what it does. There is no wasted text, though it is arguably too sparse to cover necessary details, which is a minor structural drawback.

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 has no parameters, no output schema, and no annotations, so the description must compensate. 'Backup files only' is far too minimal to fully inform an agent about what the tool does, how to use it, or what to expect afterward. It leaves critical gaps about the backup process, storage, and how to access the backup.

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?

With zero parameters, the baseline for parameter semantics is 4. The description adds meaning beyond the empty schema by clarifying the scope (files only, no database), which is the sole relevant semantic detail.

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 clearly states it backs up files only, using a specific verb ('Backup') and resource ('files'), and explicitly excludes the database. This distinguishes it from sibling tools like wordpress_backup_database and wordpress_full_backup, though it doesn't detail what 'files' includes (themes, plugins, uploads, etc.).

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 implicitly conveys when to use this tool (when a file-only backup is needed) but doesn't explicitly contrast it with alternatives or state exclusions. Given the sibling context, the agent can infer the use case, but there is no direct guidance such as 'use wordpress_backup_database for database-only backups'.

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