Set Wordpress Search Visibility

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

Annotations already declare destructiveHint=true and idempotentHint=true; the description adds real value by explaining that false is a soft request to search engines (WordPress "discourage search engines") rather than a hard block, and that true restores indexing—disclosing reversibility. It omits permission requirements and propagation delay, which keeps it below 5.

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?

Two tight sentences: the effect first, then the branch semantics. Every clause carries information; nothing is redundant with the schema or annotations.

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?

For a 3-parameter mutation with no output schema, the description covers effect, branch semantics, and reversibility, which is enough to call it correctly. Minor gaps around required auth and how long indexing changes take to apply keep it at 4.

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 67%, and the one undocumented parameter is `visible`, which the description fully explains through the true/false branches. It adds meaning beyond the bare boolean, though it doesn't reinforce domain format or dry_run behavior.

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 a specific verb pair ("Show or hide") and resource ("Cloud for WordPress site from search engines"), which is unambiguous and clearly separable from siblings like set_wordpress_version or set_wordpress_php_version.

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?

Gives a clear usage context ("useful while a site is being built") that tells the agent when to set visible=false. It lacks explicit when-not guidance or a named alternative, but no close sibling competes for this operation.

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