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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety/network profile is covered. The description adds useful payload scope (it exposes seller profile, public comments, and similar listings), but says nothing about rate limits, auth, or pagination. With annotations carrying the safety burden, this adds moderate value.

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?

One front-loaded sentence with no filler; the resource and its contents come first. Slightly dense but every clause adds information about what the caller receives.

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?

An output schema exists, so return-value documentation is not required, and the description still summarizes the major payload sections. For a single-id read tool with full schema coverage and annotations, this is essentially complete; only usage routing guidance 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 the single id parameter is fully documented in the schema (including the /listing/{slug}-{id} URL format and that the slug is cosmetic). The description adds nothing beyond that, so 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?

States a specific verb+resource ("Poshmark listing detail") and enumerates the returned payload (description, photos, size/brand/condition, seller profile, comments, similar listings), which lets an agent distinguish it from the poshmark_search/category/brand siblings. It stops short of naming an alternative explicitly, so a 4 rather than 5.

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?

No when-to-use or when-not-to-use guidance is given, and no sibling is named. The agent must infer from the word "detail" that this is the single-item fetch used after poshmark_search returns an id. No prerequisites or edge cases mentioned.

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