wordpress_advanced_wp_db_import

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

No annotations provided, so description carries full burden. It effectively discloses destructive behavior ('replaces current database') and authorization requirements. Missing operational details like transaction behavior, rollback capability, or sync/async nature.

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?

Three sentences with zero waste: operation definition, destruction warning, auth requirement. Front-loaded with critical safety info. '[UNIFIED]' prefix is tolerable 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?

Adequate for safety-critical context (destructive import) given no output schema, but incomplete regarding parameter semantics and operational behavior. The 0% schema coverage leaves significant documentation gaps unfilled.

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 has 0% description coverage. While 'from SQL file' implies file_path usage, the description fails to explain the file_path vs url relationship (mutually exclusive sources?), site identifier format, or skip_optimization purpose. Must compensate for schema gaps but doesn't.

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 specific verb (Import) + resource (database) + source (SQL file). The 'DESTRUCTIVE' warning clearly distinguishes this from sibling query/export operations like wordpress_advanced_wp_db_export or wordpress_advanced_wp_db_query.

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 critical prerequisites ('Requires admin scope') and impact warnings ('DESTRUCTIVE'), which implicitly guide usage. However, lacks explicit 'when to use' guidance distinguishing this from wordpress_wp_db_import or restoration alternatives.

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