wordpress_wp_search_replace_dry_run

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

Discloses that the tool only previews changes and never modifies the database, which is critical behavioral information. With no annotations provided, the description carries the full burden, but lacks details on idempotency, side effects, or the exact nature of the preview output.

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 extremely concise, consisting of two short sentences. It front-loads the key information (search and replace, dry run only). While it could include more parameter details without becoming overly verbose, the current structure is efficient.

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?

Given the four parameters, no output schema, and no annotations, the description lacks important details such as the format of the preview output, behavior when 'tables' is null, and any constraints on string values. This insufficient completeness could lead to incorrect tool usage.

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 description coverage is 0%, meaning the schema provides no parameter explanations. The description mentions 'site', 'old_string', and 'new_string' implicitly through the tool's action, but does not explain any parameter in detail, especially the optional 'tables' parameter. This is insufficient for an agent to understand parameter usage.

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 it performs a search and replace dry run, previewing changes without making actual modifications. The title and description explicitly emphasize 'DRY RUN ONLY' and 'NEVER makes actual changes', leaving no ambiguity about its purpose.

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?

Explicitly recommends using this tool for migration planning, providing clear context. However, it does not specify when not to use it or list alternative tools for actual changes, though the indication 'DRY RUN ONLY' implies such distinction.

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