wp_search_replace

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

Annotations already indicate destructive behavior. The description adds critical behavioral details: the mandatory dry-run first, the need for a confirmation token, and the default inclusion of --precise and --all-tables-with-prefix when table='all'. This significantly enhances transparency beyond annotations alone.

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 two sentences: the first states purpose and default, the second gives critical usage instructions. Every word adds value, and key information is front-loaded.

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 description covers the essential workflow (dry-run, confirmation token) and important defaults. However, it does not explain the site_id parameter or constraints on find/replace. Since an output schema exists, return values need not be described. Overall, it provides sufficient context for safe usage but could be more thorough.

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 only 14% schema description coverage, the description adds some parameter context (default table, default precise, flag behavior for table='all') but does not explain other parameters like site_id, find, replace, or confirmation. More detail would be beneficial given the low schema coverage.

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 tool runs `wp search-replace` against wp_postmeta for updating Elementor content, providing a specific verb and resource. It mentions default table and flags but does not explicitly differentiate from sibling tools like `bulk_find_replace_site` or `elementor_find_replace`.

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 explicitly instructs to always dry-run first and requires a confirmation token for the apply call, providing clear when-to-use guidance. However, it does not mention alternative tools or scenarios where this tool should not be used.

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