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

Annotations already cover read-only, idempotent, open-world and non-destructive. The description adds genuinely new context beyond them: pagination scope ('all pages'), the data source ('activity feed, comments filter'), and a cost signal ('1 point per returned record'), which is useful for budget-aware agents.

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 what the tool returns, and every clause earns its place by adding source, scope, or cost information.

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 simple read tool whose annotations carry the safety profile, the description covers source, pagination scope, and cost. With no output schema, it could say a bit more about the comment record shape, but the essential calling information is present.

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 all three parameters (user, max_items, start_page) are already documented in the schema. The description adds no syntax or format detail beyond what the schema provides, so 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 specific verb+resource: comments of a Product Hunt user, and clarifies the source (activity feed, comments filter). This implicitly distinguishes it from sibling activity-type tools like run_producthunt_users_upvotes, run_producthunt_users_launches and run_producthunt_users_stacks, though it does not name them.

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 (fetch a user's comments), but there is no explicit when-to-use, when-not, or named alternative. The agent must infer that the other run_producthunt_users_* siblings cover different activity types.

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