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

Annotations already establish readOnly, idempotent, non-destructive, so safety is covered. The description adds genuinely non-schema context — the call is free and needs no key — plus an inventory of what is returned (products, badge, buy call). However it does not say whether the shop is public or owner-only, nor what an empty/unregistered shop looks like.

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?

A single compact sentence with no wasted words, and the core resource is front-loaded. But the compression is achieved by unexplained domain terms ('Word Pass badge', 'the buy call') rather than by precision.

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 no output schema, the description does the work of listing the major return components (recommended/resold products, badge, buy call), which is the main thing an agent needs. What is missing is minor: the meaning of 'buy call' and whether the shop view is public.

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?

Only one parameter (agent_id) and schema coverage is 100%, including the ag_ prefix example and a pointer that register_agent returns it. The description adds nothing about the parameter, so the baseline 3 for high schema coverage 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 says this returns an agent's shop — the products it recommends and resells plus a Word Pass badge and 'the buy call' — so the resource is identifiable. But there is no explicit verb, and 'the buy call' is unexplained jargon that an agent cannot interpret without opening the tool. It sits alongside shop_add, shop_remove, resell and get_listing without clarifying the boundary.

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 when-to-use guidance, no mention of alternatives (get_listing, shop_add, shop_remove), and no indication of whose agent_id to pass beyond what the schema says. The only usage-adjacent note is 'Free, no key', which is access info rather than selection guidance.

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