get_listing_details

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

No annotations are provided, so the description carries full responsibility. The 'get' verb implies a read operation, but it does not disclose auth needs, rate limits, or error behavior. The phrase 'full details' is vague about the response structure or contents.

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 sentence, front-loaded with the action, zero filler. It efficiently conveys the core purpose and input method without any unnecessary words.

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 simple one-parameter lookup tool with no output schema, the description covers the essential scenario: what to expect (full details) and how to specify the target (ID or URL). It could be improved by stating the return format or not-found behavior, but these are minor gaps for a low-complexity read tool.

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%: the parameter is fully described as 'Listing ID or full Poshmark listing URL'. The tool description merely repeats this ('by ID or URL') and adds no extra meaning, so the baseline score of 3 for high coverage applies.

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 clearly states the verb ('Get'), the resource ('full details of a specific Poshmark listing'), and the input method ('by ID or URL'). It is distinct from siblings like search_listings or get_my_closet, which serve different lookup purposes.

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?

Usage is implied: call this when you have a listing ID or URL and need full details. However, there is no explicit guidance about when to choose this over sibling tools such as search_listings or get_my_closet, nor any when-not-to-use exclusions.

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