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

readOnlyHint=true is consistent with a metadata-discovery tool, and the description reinforces that by describing only retrieval behaviour. It adds real context about what each call yields before any query is attempted, though it does not cover error behaviour, auth prerequisites, or rate limits.

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?

Step-numbered layout is front-loaded and scannable, with required actions clearly separated from optional ones. Minor slack in the parenthetical about available_actions already being in the accounts response, which is stated after the call is described.

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?

Given an output schema exists, return values needn't be spelled out, and the description covers the critical prerequisite chain that would otherwise cause failed calls. It stops short of explaining the unaddressed `platform` parameter or what to do if an action name is invalid.

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%, so the description must carry parameter meaning — and it largely does: it explains all four `request` enum values, that `actions` takes action identifiers from available_actions, and that brands requires brand_id plus workspace_id. The gap is `platform`, which is never mentioned, and the string-or-array flexibility of `actions` is not clarified.

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?

The description frames the tool as a planning/discovery helper and enumerates its four request modes with the concrete payload each returns (workspace_id, brand_id, available_actions, action request bodies). That is specific enough to distinguish it from a data-fetching sibling, though the naming ('Helper for planning') and the 'Shopify Setup Helper' title are broader than the actual InsightfulPipe scope.

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 ordered workflow: Step 1 accounts, Step 2 actions_details marked 'REQUIRED before querying', plus clearly labelled Optional calls. Each mode is given a use case and the 'already included in accounts response' note prevents an unnecessary call. This is as close to prescriptive routing as a description gets.

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