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

The annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=true, so the description's 'Read-only' is a restatement of structured data rather than new information. Nothing is said about pagination, result size, or whether stores must be connected first, so it adds essentially nothing beyond the annotations.

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, front-loaded with the resource and platform scope, with zero filler. Nothing needs trimming, though there is also nothing extra offered.

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 read-only listing tool with no output schema, the definition covers the core identity but omits filtering behavior, pagination, and the brand_id parameter. It is minimally viable rather than complete.

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?

Three parameters at 67% schema coverage, and the description addresses none of them. In particular brand_id is undocumented in both places, and the description implies workspace scoping only, leaving brand-level filtering and the opaque 'query' override for endpoints with sparse schemas entirely unexplained.

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 (List) and resource (ecommerce stores) and even enumerates the supported platforms (Shopify, WooCommerce, Etsy, Wix), which tells the agent exactly what comes back. It does not, however, distinguish itself from the adjacent aidelly_get_ecommerce_store or aidelly_list_ecommerce_products siblings, so plural-vs-singular scope must be inferred.

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?

No guidance on when to call this versus aidelly_get_ecommerce_store (single store) or aidelly_list_ecommerce_products (store contents), and no mention of prerequisites or filtering conditions. The agent is left to infer usage purely from the name.

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