wordpress_export_content

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

No annotations are provided, so the description carries the full burden. It only says 'Export posts/pages as WordPress XML' but does not disclose behavioral traits like whether it's read-only, what the output format looks like (e.g., file download vs. string), or if any permissions are needed. This is a minimal statement with no side-effect or return-value information.

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, front-loaded sentence without redundant words or repetition of the tool name. It is appropriately terse for a simple tool, though it could potentially add a bit more structure without becoming verbose.

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 output schema, so the description should explain what the tool returns or produces. It doesn't say whether the XML is returned directly, saved to a file, or otherwise delivered. Given the minimal context and no annotations, the description is incomplete for an agent to know the invocation 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?

With zero parameters, the schema already provides full coverage (100%). The baseline for 0-param tools is 4, and the description adds no unnecessary parameter details. No additional semantic explanation is needed.

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 an export operation on 'posts/pages' with output format 'WordPress XML'. The verb 'Export' and resource 'posts/pages' make the purpose specific. However, it doesn't fully distinguish from backup/import siblings or specify scope (e.g., all posts/pages or selected).

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 provides no guidance on when to use this tool versus alternatives such as full_backup or import_content. It doesn't mention any prerequisites, exclusions, or context where this tool is preferred.

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