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

Annotations blanket-flag this as destructive/non-idempotent, but the tool actually mixes safe reads (list, get) with irreversible writes (delete_item, delete_collection, delete_photo, cancel). The description enumerates those delete/cancel actions, implicitly signaling which are dangerous, but never states permissions, whether deletions are recoverable, or what the coarse destructive hint really applies to.

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?

The purpose is front-loaded in the first sentence, then the module/action matrix follows in a compact semicolon-delimited list. It is long but dense and non-repetitive; almost every token conveys valid values the agent must choose from.

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 four-parameter mega-dispatcher with a nested free-form data object and an output schema (so returns need no explanation), the description supplies the module/action taxonomy and a discovery path (help) for the opaque payload. A little more on the data object's shape per module would make it fully self-sufficient.

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, but the description arguably does more: it enumerates the valid module values and their per-module action verbs, and explains that the data object's fields must be discovered via action "help". That is meaningfully beyond the generic schema blurb.

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+resource: "set up or change the live parts the owner manages," and enumerates the concrete domain (prices, bookings, products, posts, photos, events, quote requests, notices). An agent can tell this is the site-content administration surface, though it never explicitly contrasts itself with siblings like update_site or preview_site.

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 operational instructions: use action "help" to see a module's fields, and omit module to see what the plan includes. It also maps each module to its allowed actions, which tells the agent what to pass. It stops short of stating when this tool should be preferred over a sibling, so no exclusions are given.

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