poshmark_closet

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

With no annotations, the description carries the full burden and excels: it discloses credential-free access, public data sourcing (server-rendered page and JSON API), the pagination behavior (profile omitted on subsequent pages), and the normalized output shape. This goes well beyond a typical tool description.

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 four sentences, front-loaded with the core purpose, then pagination, then data source. Every sentence is informative with no fluff or repetition; it's efficiently structured.

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?

Given two parameters, no output schema, and no annotations, the description covers all critical aspects: return contents, pagination mechanics, first-page vs subsequent-page behavior, and data provenance. It is complete enough for an agent to invoke and interpret results correctly.

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?

The input schema already covers both parameters at 100%, and the description adds valuable context: it explains that max_id is an opaque pagination cursor and gives the exact flow (fetch without max_id first to get seller fields). This enriches the schema's terse descriptions.

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 opens with a specific verb and resource: 'Get Poshmark seller closet (storefront).' It clearly delineates what is returned (profile, reputation stats, listings, total count), distinguishing it from sibling tools like poshmark_listing or poshmark_search.

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 provides strong usage context: it explains how to fetch the first page (without max_id) and subsequent pages (pass next_max_id back). It implies when to use this tool (when you need a seller's storefront), but doesn't explicitly name alternatives or exclusions.

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