poshmark_listing

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

With no annotations, the description carries the transparency burden. It discloses that the data is public, credential-free, sourced from Poshmark's server-rendered page, and normalized. This is strong for a read-only tool, though it stops short of mentioning potential scraping limitations or rate limits.

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, front-loaded with the core purpose, and every sentence adds value: what the tool returns, the composition of the response, and the data source/authentication context. No fluff 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?

Given there is no output schema, the description does well to enumerate the return content: full listing details, seller profile, public comments, and similar listings. It would be slightly stronger with explicit mention of error behavior or the exact response shape, but for a single-parameter detail fetcher it is sufficiently 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?

The input schema fully documents the single parameter 'id' with an explicit extraction rule from listing URLs. The description adds no further parameter detail, but since schema coverage is 100%, the baseline of 3 is appropriate.

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 'Get Poshmark listing detail,' which clearly names the verb and resource. It further distinguishes this from sibling Poshmark tools by specifying the full page-level content returned, such as listing data, seller profile, comments, and similar listings.

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 makes the use case clear: retrieve detail for a specific Poshmark listing. It adds context that this is credential-free public data, implying no auth setup is needed, though it does not explicitly name alternatives like poshmark_search or poshmark_closet.

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