wordpress_advanced_wp_db_export

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

No annotations provided, so description carries full burden. Mentions file creation side-effect (timestamped backup in /tmp) but omits critical operational details: table locking behavior, permission requirements, memory/disk space requirements, or whether the operation is blocking. '[UNIFIED]' prefix appears to be metadata leakage without explanation.

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?

Two sentences, appropriately brief. However, '[UNIFIED]' prefix appears to be implementation metadata polluting the description rather than helpful context for the agent. Content is front-loaded with action but could remove metadata noise.

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?

Severely incomplete given 0% schema coverage and lack of annotations/output schema. For a database export tool, should document parameters (especially table filtering options), distinguish from basic export sibling, and warn about disk space or permissions. Current description insufficient for safe operation without additional schema documentation.

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% (no parameter descriptions in schema). Description completely fails to compensate—it mentions none of the 4 parameters (site, tables, exclude_tables, add_drop_table). Agent cannot infer what 'tables' array expects, format of 'site' identifier, or behavior of 'add_drop_table' without guessing.

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?

Clear verb ('Export') + resource ('WordPress database') + output format ('SQL file'). Mentions specific output location ('/tmp directory') and timestamping behavior. However, it doesn't explicitly distinguish from sibling 'wordpress_wp_db_export' or explain what makes this 'advanced' vs the basic version.

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?

No explicit when-to-use or alternative guidance. Only contextual clue is the output location (/tmp), which hints at temporary storage vs permanent backup location. Missing guidance on when to use 'advanced' vs standard export sibling.

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