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

Annotations already cover the safety profile (readOnlyHint) and open-world nature, so the bar is lower. The description still adds real context: credential-free public data, the two distinct upstream sources (server-rendered page vs. JSON pagination API), and the pagination field-omission behavior. It stops short of describing rate limits or response shape, which the output schema covers.

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?

Front-loaded with the core purpose and pagination mechanic in the first two sentences, then sourcing detail. It is slightly repetitive, restating the id/slug explanation already present in the schema, but no sentence is wasted filler.

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?

For a 2-parameter read tool with an output schema and annotations, the description covers purpose, pagination workflow, data provenance, credential requirements, and the sibling alternative. Nothing an agent needs to invoke it correctly is missing.

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% and both parameters are fully documented in the schema, so the baseline is 3. The description repeats the id explanation (trailing /trend/{slug}-{id} segment, cosmetic slug) verbatim from the schema rather than adding new syntax or format detail.

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?

States a specific verb and resource — returns a page of normalized listings for a curated trend/showroom collection — with a concrete example and an explicit link to Poshmark's own trend pages. It clearly distinguishes itself from poshmark_search, so an agent can route between them without opening either schema.

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?

Explicitly names the alternative (poshmark_search) and the condition under which it applies. It also states exactly how to paginate by passing next_max_id back as max_id, leaving nothing about when/how to use the tool to inference.

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