poshmark_category

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

No annotations exist, so the description carries the full burden. It discloses credential-free public access, the source (server-rendered category page and JSON pagination API), and pagination behavior. It does not mention rate limits or error cases, but covers key behavioral aspects for a read-only browse 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?

Three sentences with no filler. The first sentence states the core action, the second adds context, and the third explains pagination and data source.

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?

The description is sufficient for a paginated browse tool: it covers input, output page concept, pagination cursor, and access model. Without an output schema, it stops short of listing returned fields, but the 'normalized Poshmark listings' phrase gives a reasonable expectation.

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 schema already describes both parameters (100% coverage). The description adds value by giving concrete path examples and explaining the max_id flow ('previous response's next_max_id'), reinforcing the schema without redundancy.

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 'Browse Poshmark listings by category' and specifies it returns 'a page of normalized Poshmark listings for a given category path.' Examples like 'Women-Shoes, Men-Shirts' ground the concept, distinguishing it from sibling tools like poshmark_search or poshmark_brand.

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?

It gives concrete usage context: 'same browsing view as Poshmark's own category pages' and explains pagination via 'Pass a previous response's next_max_id back as max_id to fetch the next page.' It does not explicitly mention alternatives or when-not-to-use, but the browsing semantics are clear.

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