wordpress_wp_db_export

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

With no annotations provided, the description carries full burden. It adds valuable context about output location (/tmp) and file naming (timestamped), but lacks critical behavioral details such as table locking behavior, memory usage, return value format, or permissions required for database reads.

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?

Efficient two-sentence structure with specific details. The '[UNIFIED]' prefix appears to be metadata noise that doesn't aid agent understanding, but otherwise no wasted words.

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 database export operation with no output schema and no annotations, the description should disclose the return value (file path? success status?) and side effects. It mentions the output file location but omits what the tool returns to the caller.

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 coverage is 0% and the description completely fails to explain the single required parameter `site` (likely a domain or site identifier), leaving the agent with no semantic guidance on how to populate this field.

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?

Clearly states the action (export), resource (WordPress database), output format (SQL file), and location (/tmp directory). However, it fails to distinguish when to use this versus the sibling tool `wordpress_advanced_wp_db_export`.

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?

Provides no guidance on when to use this tool versus alternatives, prerequisites (e.g., required permissions), or when not to use it (e.g., large databases during peak traffic).

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