wp_replace_shortcode

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

With no annotations, the description carries the full burden, but it only discloses that the tool replaces content and may filter by attribute. It does not state what happens to the original shortcode, whether changes are reversible, required permissions, failure behavior when no match is found, or that dry_run can preview the change.

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?

A single, front-loaded sentence with no filler. It states the core action immediately and adds the optional matching behavior in a second clause. Every word contributes.

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?

This is a mutating tool with 7 parameters, no annotations, and no output schema. The description is too sparse to fully support invocation: it omits expected return values, error cases, permission requirements, and how occurrence/disambiguation rules affect the operation, though the schema does fill in some parameter details.

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 100%, so the baseline is 3. The description adds minimal context by tying 'specific shortcode' to the tag parameter and 'optionally match an attribute value' to match_attr/match_value, but most parameter meaning already exists in the schema.

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 states a clear verb ('replace') and resource ('specific shortcode in a page'), and the optional attribute matching adds precision. It is distinguishable from sibling tools like wp_insert_shortcode or wp_list_shortcodes, though it does not explicitly name alternatives such as wp_elementor_update_shortcode_content.

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?

There is no guidance about when to use this tool versus alternatives like wp_insert_shortcode, wp_elementor_update_shortcode_content, or wp_blocks_replace. The description implies a use case ('specific shortcode', 'optionally match attribute value') but never states exclusions or selection criteria.

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