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 usefully discloses the billing model ('1 point per returned record'), which is real behavioral context, but says nothing about pagination interaction with start_page/max_items, auth or rate-limit behavior, or what a returned record contains.

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?

Two short sentences, front-loaded with the core action, and the cost caveat is tacked on efficiently. The parenthetical '(username, name, avatar, home region)' is slightly ambiguous as to whether it lists match targets or returned fields, which is the only real friction.

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?

With no output schema and no annotations, the description should say more about what a result contains (the parenthetical hints at profile fields but is unclear) and how paging works. It is adequate for invocation but leaves return-value expectations underspecified.

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%, with every parameter documented including defaults, enum values, and a query example, so the schema does the heavy lifting. The description's 'by name or handle' merely restates the query parameter and adds no syntax or constraint detail beyond it.

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 and resource ('Search Poshmark closets') plus the lookup key ('by name or handle'), which separates it from run_poshmark_users (single-user lookup) and run_poshmark_items_search. However, it never names a sibling tool to route the agent explicitly, so it falls short of a 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?

Usage is only implied: an agent infers this is the tool for finding a user when it has a partial name/handle. There is no statement of when-not-to-use it or which sibling to prefer for a direct handle lookup, but the 'by name or handle' phrasing and the cost note give some practical context.

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