poshmark_search

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

With no annotations, the description carries the full burden of behavioral disclosure. It explicitly states that data is 'credential-free public data', describes the exact return payload (normalized listing summaries with fields, total count, opaque pagination cursor), explains how pagination works, and names the data sources (server-rendered page and JSON API). This is comprehensive transparency.

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 three sentences long, front-loaded with the core action, and every sentence adds value: scope, return payload, pagination, and data source. No redundancy or filler, making it highly efficient.

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 no output schema, the description effectively explains the return values (normalized fields, total count, cursor). It also covers pagination, optional department filtering (implied via schema), and the public/credential-free nature. This is complete for a search tool with a moderate parameter set.

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% with each parameter having its own description. The description adds pagination context ('Pass a previous response's next_max_id back as max_id') but this largely mirrors the schema's max_id description ('Opaque pagination cursor from a previous response's next_max_id'). No significant new parameter-level meaning is added beyond the schema.

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 starts with the specific verb 'Search' and identifies the resource as 'Poshmark listings', thus clearly stating its function. It further specifies the scope ('clothing, shoes, and accessory listings'), which distinguishes it from sibling tools like poshmark_listing (likely single listing) and other marketplace search tools.

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 clearly establishes that this tool is for searching Poshmark listings and explains the pagination flow. It gives context on what the tool is used for but does not explicitly mention alternatives or when not to use it, so it misses the 'exclusions' part of a 5.

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