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

No annotations are provided, so the description carries the full behavioral burden. It usefully discloses the billing model ('Flat 5 points per successful run') and that likers/comments are limited to what is 'shown on the page,' but it omits auth requirements, error behavior on invalid ids, and any rate-limit or retry semantics.

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?

Two tight sentences: the first is a front-loaded purpose-and-return summary, the second adds cost information. No filler, no 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?

Because no output schema exists, the description's field list (price, brand, size, colors, category, photos, likes/comments, seller, likers/comments) is valuable for setting return expectations. With full schema coverage for inputs and clear scope, the definition is nearly complete, though it could say more about usage boundaries versus siblings.

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%, so both parameters (item, domain) are already documented in the schema with format and enum details. The description adds minor context by mentioning id or URL, but the domain option and its default are left entirely to 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?

States a specific verb ('Get') and resource ('one Poshmark listing') and enumerates the returned fields, which distinguishes it from sibling search tools that return multiple listings. It does not explicitly name any sibling alternative, so it stops short of the top score.

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 implies usage when an id or URL is available, but it gives no explicit when-to-use guidance, no exclusions, and no routing to siblings like run_poshmark_items_search or run_poshmark_items_related. The context is inferable but not stated.

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