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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds essentially nothing behavioral beyond the name: no pagination notes (the cursor mechanics live only in the schema), no result ordering, and no rate/auth context.

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 tight sentence with the purpose up front and no filler. It is appropriately sized for a simple two-parameter browse tool, though it is arguably too terse to earn a 5.

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?

The tool is simple: read-only, two well-documented params, an output schema that covers return values, and annotations for safety. That structured data makes the description nearly sufficient, but the lack of any sibling disambiguation leaves a small gap for selection.

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 name and max_id, including the /brand/{name} URL convention and cursor semantics. The description's only addition is the '(e.g. Nike)' example, matching the baseline 3 for a fully-covered schema.

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 (browsed) and resource (listings) with a scoping qualifier (by brand name) and an example (Nike). It is clear what the tool returns, but it does not differentiate itself from close siblings like poshmark_brands or poshmark_search within the same Poshmark family.

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 use case (browse listings for a brand) is implied by the description, but there is no explicit when-to-use guidance, no mention of when a general poshmark_search would be preferable, and no prerequisites called out.

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