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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds value beyond that: 'all pages' signals automatic full pagination, and '1 point per returned record' discloses the credit cost model, which is operationally important for an agent. It does not describe error or rate-limit behavior, keeping it short of a 5.

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 with no filler. It packs scope, return fields, pagination and pricing into one line, though the telegraphic phrasing ('all pages', '1 point per returned record') could be slightly clearer.

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 3-parameter read tool with full schema coverage, no output schema, and annotations covering safety, the description is sufficient: it identifies the resource, the return fields, pagination scope, and cost. Remaining gaps (error behavior, pagination interaction with max_items) are minor.

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 schema already documents user, max_items (up to 250, default 25) and start_page. The description adds nothing about parameter format or constraints, so the baseline 3 applies.

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 clear verb+resource: launches submitted by a given Product Hunt user, and names the returned payload (votes, comments, ranks, dates). This is distinguishable from siblings like run_producthunt_users_upvotes or run_producthunt_users_comments by resource alone. It does not explicitly name a sibling alternative, so a 4 rather than 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 implied by the resource ('launches submitted by a user'), and an agent can infer it is the per-user launches endpoint. However there is no explicit when-to-use / when-not-to-use guidance and no mention of alternatives such as run_producthunt_launches_search for launch-centric queries.

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