get_my_closet

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

No annotations are provided, so the description carries the full burden. It states the default behavior (authenticated user) but does not disclose read-only nature, authentication requirements, rate limits, or potential side effects. There is no mention of what happens if the user is not authenticated or if the username is invalid.

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 a single sentence with no wasted words. It front-loads the action and resource, making it easy to parse.

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 list tool, the description is adequate but lacks details about the return format, default limit/status behavior, and how it relates to searching all listings. However, given the schema includes limit and status, and the complexity is low, this is a minor gap.

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 covers all parameters with descriptions (100% coverage), but the description adds meaning by clarifying that the tool operates on the authenticated user's closet by default and that username can be used to view other closets. This complements the schema's bare 'omit to use logged-in user'.

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 uses a specific verb 'List' and specifies the resource 'items in a Poshmark closet', with a note about defaulting to the authenticated user. This distinguishes it from sibling tools like search_listings (which searches all listings) and get_listing_details (which gets a single listing).

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 guidance is provided on when to use this tool versus alternatives. It does not mention when to prefer this over search_listings, nor does it specify exclusions (e.g., when you need sold items, use a different approach). The context is implied but not explicit.

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