wordpress_wp_db_export

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

The description discloses that the export creates a file in /tmp with a timestamped name, which gives insight into output location and naming. However, with no annotations, it does not mention whether the operation is read-only, auth requirements, or if it overwrites existing files. Still, the provided details are relevant and additive.

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 concise: a single sentence that covers purpose, output, and destination. No redundancy, and front-loaded with key information.

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 simple tool with one parameter and no output schema, the description gives essential info (file location, backup purpose) but lacks explanation of the parameter and any side effects or constraints. It is adequate but incomplete for full autonomous use.

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?

The schema has one required parameter 'site' with no description, and the tool description does not explain what 'site' refers to (e.g., site URL, ID). With 0% schema description coverage, the description fails to compensate, leaving the agent unsure how to specify the target site.

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 the action (export), resource (WordPress database), target format (SQL file), and destination (/tmp directory). It also mentions timestamping and backup purpose, distinguishing it from other WordPress tools that manage posts, media, or cache.

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 implies use for backup/recovery but provides no explicit guidance on when to use this tool versus alternatives (e.g., wordpress_export_content for content export, or wp_db_check for integrity). No context on prerequisites or when not to use it.

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