Create Wordpress Backup

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

Annotations only declare the safety profile (readOnlyHint=false, idempotentHint=false, destructiveHint=false). The description adds behavior beyond that: asynchronous completion ('appears in list_wordpress_backups when finished, usually within a few minutes') and the quota constraint with its exact error code, which is not visible anywhere in the structured fields.

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?

Three tight sentences: what it does, why/when, then the constraint and the observable outcome. The critical quota warning is placed before the completion note, and nothing is redundant.

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?

With no output schema, the description compensates by explaining where the result surfaces (list_wordpress_backups) and the expected latency. Combined with full schema parameter coverage, an agent has everything needed to invoke it and handle the quota error.

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 description coverage is 100%, and all three parameters (domain, dry_run, staging) are documented in the schema itself. The description adds no further meaning about dry_run preview semantics or staging targeting, so the baseline of 3 applies.

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 opens with a specific verb and resource: 'Take an on-demand backup of a Cloud for WordPress site's files and database.' It also scopes the operation as on-demand/now, which separates it from scheduled backups and from siblings like list_wordpress_backups and restore_wordpress_backup without needing the schema.

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?

It gives an explicit use case ('before a risky change') and a hard precondition with a concrete failure mode: only one on-demand backup of each type may exist, so delete the old one first or get BACKUP_FAILED 'Quota Reached.' The agent knows both when to call it and what blocks it.

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