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

Annotations already declare destructiveHint=true, readOnlyHint=false, and openWorldHint=false, so the safety profile is covered. Beyond that, the description adds nothing: it does not say the edit mutates the live site, whether it is reversible, whether it requires a version/publish step, or what happens to sibling elements matched by the same selector.

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 short sentences with the action front-loaded and no padding. The trailing 'Used by the card' is a bit cryptic and arguably costs more in ambiguity than it earns.

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?

An output schema exists so return values need not be covered, but this is a destructive mutation with a nested selector object and an undocumented site_id. An agent still lacks enough to construct the element locator confidently or understand the consequences of the write.

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 only 50%: path and request are documented, but site_id and the nested element object's tag/text/classes fields have no descriptions, and the description does not explain how those three fields act as a locator. 'The way they asked' does signal that request is freeform user language, which is a small genuine addition.

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 and resource: changing the part of a WebTwizz site the user clicked, driven by the user's natural-language request. The action is clear, but it gives no differentiation from near-neighbours such as edit-text, edit-site, or update-site, leaving the agent to guess which editing tool applies.

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?

'Used by the card' plus 'the part... the user clicked in the card preview' implies the triggering situation: a preview-driven, element-targeted edit. However, there are no exclusions and no named alternative, so the boundary with edit-text (also text/element editing) is left entirely to inference.

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