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

Goes well beyond the annotations: it discloses that output lands in an uploads subfolder (ab-mcp-exports) under an unguessable name, that no URL is returned, that each call writes a new file, that Apache .htaccess protection may not apply on nginx, and that MCP file tools cannot reach the folder so deletion must happen over filesystem/SFTP. This is exactly the safety and retrieval context an agent needs, and it is consistent with readOnlyHint=false, idempotentHint=false and destructiveHint=false. It loses a point only because the explanation is dense enough that the operationally critical fact (file is not retrievable via MCP file tools) is buried mid-paragraph rather than flagged up front.

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 sibling alternative are front-loaded, and the sentence about no-match exports still yielding a WXR file prevents a common misread. However, the middle section stacks several long clauses and repeats the same protection idea twice (unguessable filename vs. unguessable name), which could be compressed.

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?

No output schema exists, and the description compensates by naming the return fields (exported, file, path, upload_path, bytes, retrieve_with, a note) and explaining how to retrieve and delete the produced file. Combined with the capability requirement and error semantics, an agent has everything needed to call this correctly and act on the result.

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 the schema already documents status and post_type in comparable detail, so the description does not need to restate them. It adds no syntax or edge-case guidance for the two parameters (for example which post types accept a status filter beyond the schema note), so it sits at the baseline for a fully documented 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?

States a specific verb and resource (export content as a WordPress WXR file) and immediately scopes it against the sibling wp_blueprint_export, which handles structure/settings instead. An agent can distinguish the two without opening either 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?

Names the alternative tool and the axis that separates them (content export vs. site blueprint), states the required export capability, and clarifies that a zero-result export is still a success. The condition selecting the alternative is explicit rather than inferred.

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