List membership tiers

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so safety is covered. The description adds a concrete rate limit (100 requests / 10 seconds per shop) plus a link to the rate-limiting guide, which is real behavioral context not present in the structured fields.

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?

Very short and front-loaded, with every sentence earning its place. The rate-limit notice is placed before the purpose statement, which slightly buries the actual function, but no wording is wasted.

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?

A simple, read-only, zero-required-parameter list tool with full annotation coverage and no output schema, so the bar is low. The description covers scope and rate limits; only pagination/return-shape hints are absent, which is acceptable given the tool's simplicity.

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%; the single 'account' parameter is already fully explained in the schema as 'Exact private shop profile label; not a provider identity or authorization proof.' With one optional param and complete schema documentation, the baseline of 3 applies — the description adds nothing about the parameter.

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 and resource ('Lists all tiers') and scopes it to 'the current shop'. It is distinguishable from the many list_* siblings (list_members, list_accounts, list_collections), though it does not explicitly contrast itself with them.

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 alternatives such as list_members or get_member, and no stated prerequisites. The only usage context is the implicit 'current shop' scope.

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