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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description usefully discloses what the payload contains (profile fields plus listings) and that filters are optional, but says nothing about pagination or listing limits, which matters for a listings-returning tool.

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 front-loaded sentence that leads with what the tool returns and follows with the optional filters. Efficient, though the parenthetical field list makes it slightly run-on.

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 structure need not be explained, and the description does sketch the return payload. For an 11-parameter tool with zero schema description coverage, however, four parameters (sizes, gender, category, subcategory) receive no explanation anywhere.

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 coverage is 0%, so the description must carry parameter meaning. It names price, condition, colour, discount and sort as filters, mapping to price_min/price_max, condition, colours, on_sale and sort, but leaves sizes, gender, category and subcategory entirely unexplained and gives no value formats (e.g., valid sort values).

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: retrieving a Depop seller's shop, naming both the profile content (rating, sold count, followers, bio) and current listings. It is distinguishable from depop_search_sellers and depop_item, though it never names the sibling it is not.

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?

The required username parameter and 'seller shop' framing imply the usage (look up one seller's shop by username), but there is no explicit when-to-use or when-not-to-use guidance versus depop_search_sellers or depop_search.

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