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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered; the description goes well beyond that by ruling out a download capability the name might imply, explaining where downloads actually happen, and distinguishing on-demand WP Toolkit backups from nightly server backups that support restores on request.

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?

Purpose and the backup-type distinction are front-loaded in the first sentence, with the download limitation following. The WP-Cockpit navigation detail is verbose but actionable for customer-facing replies, so it earns its place; the prose is still longer than strictly needed.

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 single-parameter read-only tool with no output schema, the description covers scope, alternatives, the major capability gap and the no-WordPress edge case. It does not hint at what the listing returns (names, dates, sizes), which would help the agent reason about results, but that is a small gap.

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?

Single required 'domain' parameter with 100% schema description coverage ('Die Domain, z. B. example.de'), so the schema does the documentation work. The description adds nothing about the parameter itself, which is the expected baseline here.

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?

First sentence names a specific verb and resource (on-demand WordPress backups via WP Toolkit) and draws an explicit boundary against the nightly server backups the customer sees elsewhere. An agent can separate this from create_wordpress_backup, restore_wordpress_backup and get_backup_status without opening any 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?

Gives explicit when-to-use scope, an explicit when-not (downloading is impossible, there is no tool for it), and routes the customer to the WP-Cockpit path with concrete navigation steps. It also tells the agent what to do in the empty-result case (report clearly that no WordPress was found).

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