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

With no annotations, the description must carry the full behavioral burden. It discloses a cost model ('Flat 5 points per successful run') and implies a read-only operation ('Get'), but it omits authentication needs, rate limits, error behavior, and whether the profile is public vs private in detail.

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?

A single, front-loaded sentence that lists the key return fields and ends with the cost note. Every clause is informative and there is no wasted text.

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?

No output schema exists, so the description appropriately names the return fields (bio, location, followers/following/listing counts, items sold and activity) and the cost. It is largely complete for a two-parameter read tool, though it could mention authentication or pagination.

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% for both parameters, so the schema already documents the user and domain inputs. The description adds no extra syntax, format, or constraint details beyond what the schema provides.

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 ('Poshmark seller's public closet profile') and enumerates the fields returned (bio, location, counts, etc.). Distinguishes itself from sibling tools like run_poshmark_users_search and run_poshmark_users_followers by focusing on a single profile lookup.

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 the tool is used when you have a username or URL, but it does not explicitly say when to choose it over alternatives such as run_poshmark_users_search or run_poshmark_users_items. No when-not conditions or prerequisites are given.

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