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

With no annotations, the description carries the full burden, and it discloses one genuinely useful behavioral trait: a shop key returns only the single bound shop rather than the full membership set. Beyond that it says nothing about ordering, pagination, or the read-only nature of the call, which for an unannotated tool is a notable gap.

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 with no filler; the core scope is front-loaded and the credential caveat follows immediately. Nothing in it is redundant.

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?

Output shape is covered by the output schema, so the description need not explain return values. However, for a paginated list endpoint with two entirely undocumented parameters, the definition ought to explain paging and the key-vs-user scoping more fully to be self-sufficient.

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 0% for limit and cursor, so the schema documents neither meaning nor defaults, and the description adds nothing about paging, default page size, or how cursor values are obtained. An agent must guess the pagination contract despite an output schema existing.

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 states a specific resource (shops the signed-in person belongs to) and what is returned (each shop with the caller's role), which is enough to distinguish it from sibling mutators such as shops_create or shops_setBrand. It is elliptical rather than verb-led ('Shops the signed-in person belongs to'), but the scope is unambiguous.

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?

There is no explicit when-to-use guidance and no named alternative (e.g., me_get for identity, members_list for other people). The second sentence hints that behavior differs by credential type but leaves the agent to infer the calling context rather than stating conditions for use.

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