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

Annotations already declare destructiveHint=true, openWorldHint=true and readOnlyHint=false, so the safety profile is carried by structured data. The description adds workflow-dependency context (body must be derived from prior calls) but says nothing about irreversibility, permissions, side effects, or confirmation expectations for a destructive open-world write.

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?

Front-loaded with the workflow position and numbered prerequisites; each line carries instruction value. Slightly padded by the repeated 'xxxxxx' placeholders and the redundant IMPORTANT/REQUIRED emphasis, but overall tight.

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 explained, and the description adequately covers the nontrivial prerequisite chain for a destructive free-form dispatcher. The gap is that it never characterizes the mutation's blast radius, leaving the agent dependent on annotations alone.

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 0% and the single 'body' parameter is an unconstrained open object (additionalProperties: true), so the description must carry the load. It does useful work by directing the agent to obtain the exact body structure from query_contexts actions_details, but it provides no field-level semantics, and 'Follow the schema exactly' is unhelpful given the schema imposes no structure.

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 (execute) and resource (WooCommerce action) and positions itself as the final execution step of a three-step workflow, which distinguishes it from the read-oriented siblings (query_contexts, query_data). It never says what an 'action' concretely is, but the workflow framing makes the role unambiguous.

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 names the prerequisite tool (query_contexts) and the exact request values ('accounts', then 'actions_details' with actions from available_actions), and demands step 2 always precede execution. It gives strong 'when to use / how to prepare' guidance but no 'when not to use' or failure-mode guidance.

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