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

Annotations already flag destructiveHint=true and non-idempotent, and the description adds substantial context beyond them: previous values are backed up before every write, restore undoes the last replace, replace is a literal string swap that never rebuilds slide structure, and it also matches the escaped form URLs take in stored JSON. It even states a connector version prerequisite. This is richer than a generic mutation caveat.

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?

Purpose and the page_design contrast are front-loaded, then the action list, then workflow guidance — a sensible order. The theme-demo narrative ('Read more' button, old phone number, stale campaign headline) is slightly longer than needed to make the point, but every paragraph still carries usable information.

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?

With an output schema present, return values need not be spelled out, and annotations cover the safety profile; the description still explains backup/restore and dry-run semantics. The only shortfall is that two parameters (slide_id, site_url) are never characterized anywhere, which for a seven-parameter tool is a minor completeness gap.

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%, so the description carries the burden, and it does document action's four values ('list', 'get', 'replace', 'restore'), the slider_id targeting for 'get', and the find → replace / confirm=false mechanics. It leaves slide_id and site_url unexplained, which is a real gap given seven undocumented parameters, but the meaningful operational parameters are covered.

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?

Names a specific verb and resource ('Read and fix Slider Revolution sliders') and pins down exactly what the tool touches — slides stored in Slider Revolution's own tables. It explicitly distinguishes itself from wordpress_page_design, which 'can see the shortcode but never the button, headline or link inside the slide.' An agent can select this over sibling WordPress tools without further reading.

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 an explicit motivating scenario (leftover theme-demo content: demo URLs, old phone numbers, stale headlines) and names the sibling that cannot handle it. It also prescribes the correct workflow: 'Run replace with confirm=false first' as a dry-run before any write, and lists the four actions with their intended use. When/when-not and alternatives are all covered.

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