depop_shop

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

With no annotations, the description carries the full burden. It adds useful context by stating the data is 'public' and sourced from Depop's own shop pages, implying no auth and read-only nature. However, it does not disclose potential issues like pagination, rate limits, or behavior when a username is invalid, leaving gaps in behavioral disclosure.

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?

The description is two sentences, front-loaded with the primary purpose, then details return contents and filter options. Every sentence adds value with no filler or redundancy.

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 takes responsibility for explaining return values. It names profile fields (rating, sold count, followers, bio) and notes 'current listings' with filter options, giving a solid mental model. It falls short of fully describing listing structure or pagination, but for a shop-retrieval tool this is reasonably complete.

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 100%, so the description need not repeat parameter details. It does group the parameters into 'optional ... filters', which adds a small semantic layer, but essentially it restates what the schema already shows. Baseline 3 is appropriate since the schema does the heavy lifting.

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 clearly states a specific action ('Get a Depop seller's shop') and resource, and enumerates the return contents (profile fields plus current listings). It distinguishes from siblings like depop_item (individual item) and depop_search (search across shops/listings) by focusing on a specific seller's shop.

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 description implies use for retrieving a seller's shop with listings and profile data, but it does not explicitly state when to use this tool versus siblings like depop_search or depop_item, nor any exclusions. The mention of 'current listings' and filters hints at its role, but explicit guidance is absent.

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