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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint, so 'Read-only' in the description merely repeats structured data. The one piece of added value is scope of the response (catalogue contents plus whether the store is taking orders), which matters because no output schema exists, but there is nothing about freshness, failure on unknown slugs, 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?

One front-loaded sentence with the verb and resource first, then the contents, then a terse mode flag. No filler or redundancy to trim.

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?

With one simple parameter, full schema coverage, and no output schema, the description carries the burden of describing what comes back and does so at a useful level of specificity (prices, stock, services, shipping, order status). Missing only failure behavior and data freshness, which is a minor gap for a single-record read tool.

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 description coverage is 100% and the single parameter already documents itself as a slug obtained from find_stores, including a maxLength constraint. The description adds no syntax, format, or validation meaning beyond that, so the baseline 3 applies.

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 uses a specific verb and resource ('Read one GYSM store's catalogue') and enumerates the payload: products with prices and stock, bookable services, shipping options, and order-taking status. It does not name a sibling to distinguish itself from, though 'read one' implicitly contrasts with the discovery-oriented find_stores referenced in the schema.

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?

Usage is only implied: reading one store presupposes the agent already has a store slug, and the schema's parameter note points at find_stores as the way to obtain it. No explicit when-to-use or when-not-to-use statement appears in the description itself, leaving the routing to inference.

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