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

Annotations already declare destructiveHint=true, openWorldHint=true, readOnlyHint=false, so the safety profile is carried by structured data. The description adds a genuine behavioral fact beyond annotations: the body must be derived from a prior actions_details lookup. It does not say what gets changed irreversibly or what happens on a malformed body.

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 purpose and workflow position, then numbered steps. Some redundancy ('REQUIRED', 'IMPORTANT', repeated 'xxxxxx' placeholders) and capitalized emphasis add noise, but nothing is bloated to the point of obscuring the instructions.

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 an open-world destructive tool with an effectively unconstrained body and an output schema, the description covers the two things an agent cannot infer: the mandatory prerequisite calls and where the body shape comes from. Remaining gaps (failure handling, reversibility) are secondary given the annotations and output schema.

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% for a single free-form nested 'body' object with additionalProperties=true, so the description must compensate. It partially does by directing the agent to call request='actions_details' to obtain the exact body structure and to 'follow the schema exactly', but it never names any field of the body itself.

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 ('Execute Magento action') and positions it as the final step of a workflow, which separates it from the read-only siblings query_contexts and query_data. What exactly an 'action' is stays abstract, but the execute-vs-query distinction is clear.

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?

Explicit sequencing: step 1 request='accounts', step 2 request='actions_details' with specific action ids, plus 'Always call step 2... before executing.' This is strong when-to-use guidance naming the prerequisite tool. It does not state when NOT to use it (e.g., use query_data for plain reads), which keeps it below a 5.

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