fleet_find_replace

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

Annotations mark destructiveHint=true and idempotentHint=false. Description adds that it follows the same flow as bulk_find_replace_site but iterates across sites, returns summaries, and requires a dry-run step. No contradictions; adds valuable behavioral context.

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 front-loaded with purpose, usage guidance, and warning. Efficient but could briefly list key parameters for improved scannability.

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?

Covers high-level operation and return summaries (output schema exists). Lacks detail on parameters and exact flow per site, which is important given 6 params and destructive nature.

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 only 17%. Description does not explain most parameters (e.g., find, replace, case_sensitive, widget_type, confirmation) beyond implying 'find/replace plain text' and mentioning 'site_ids' as subset. Fails to compensate for low 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?

Description clearly states it performs find/replace plain text across every Elementor page of every site, contrasting with bulk_find_replace_site. It highlights the scope (across sites) and output (per-site + grand-total summary), making it distinct from siblings.

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 instructs to dry-run first then apply, and advises using sparingly as 'the nuclear option'. This provides clear when-to-use and caution, differentiating from alternatives.

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