create_listing

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

No annotations are provided, so the description carries full burden. It only mentions 'authenticated user' but does not disclose behavior like mutating state, auth requirements beyond basic ownership, possible validation errors, or effects on existing data. For a create tool, this is minimal.

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 main action, no unnecessary words. It is concise and to the point.

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?

This is a mutation tool with 10 parameters, no output schema, and no annotations. The description is extremely brief and does not explain return values, success/failure behavior, or prerequisites beyond 'authenticated user'. For a tool of this complexity, more context is needed for safe and effective use.

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 provides detailed descriptions for all 10 parameters (100% coverage), so the description adds no extra meaning. The baseline of 3 applies because the schema does the heavy lifting; the description doesn't clarify any parameter-specific semantics beyond what the schema already states.

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 ('Create') with a clear resource ('a new listing') and scope ('in the authenticated user's Poshmark closet'). This fully distinguishes it from sibling tools, which are read/list/search/accept operations.

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 you want to add a new listing to your closet. However, it does not explicitly state when not to use it or mention alternatives (e.g., 'use search_listings to find existing listings'). Context from siblings is clear, but no direct guidance is provided.

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