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

Beyond the annotations, which already declare read-only/idempotent/non-destructive behavior, the description adds useful context: it returns collection size and first products, covers all pages, and costs '1 point per returned record.' That billing and pagination context is meaningful for invocation planning, though rate-limit or auth details are absent.

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 resource and return contents, followed by a billing note. Every sentence contributes useful information without repetition.

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 three-parameter read-only list tool with no output schema, the description is largely complete: it names the resource, describes returned fields, notes page coverage, and discloses billing. It could better explain how 'all pages' interacts with 'max_items' and 'start_page', and how it differs from sibling collection endpoints.

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%, so the three parameters are fully documented in the schema. The description does not add meaning beyond the schema for 'user', 'max_items', or 'start_page', so the baseline 3 is appropriate.

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 clearly identifies the resource as a Product Hunt user's collections and adds distinguishing detail ('with their size and first products'), which separates it from global collection tools. It lacks an explicit verb like 'list' and does not name a specific sibling alternative, so it stops 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?

The description states what is returned but gives no guidance on when to choose this tool over siblings such as run_producthunt_collections, run_producthunt_collections_search, or run_producthunt_users_stacks. There are no exclusions, prerequisites, or alternative-selection cues.

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