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

Annotations declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds genuine behavioral context beyond that: it returns the public profile plus current active listings, and an unknown slug yields a not-found error, which tells the agent how failures surface.

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 sentences, front-loaded with what is returned, followed by slug sourcing and error behavior. No filler; each clause carries information the agent needs.

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?

An output schema exists, so return values need not be enumerated, and the description covers the profile+listings payload, slug sourcing, and the unknown-slug error. Pagination semantics (page/limit) live in the schema, leaving only minor room for additional context.

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%, so the baseline is 3, but the description adds real meaning the schema lacks by explaining what the slug represents and where it comes from. It does not add detail on page/limit/query, which the schema already documents.

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: returns a shop's public profile plus a page of its active listings, and clarifies this is the 'shop view' of a seller rather than a listing view. It is clear, though it does not explicitly name differentiating siblings such as reverb_shop_feedback or reverb_listing.

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?

Gives concrete sourcing guidance for the slug (from a listing's shop link or reverb.com/shop/{slug}), which helps the agent construct the call. However it never states when to prefer this over reverb_shop_feedback or reverb_listing, so usage is only implied rather than contrasted.

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