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

Annotations already declare readOnly, idempotent, open-world, and non-destructive, so the safety profile is covered. The description adds one genuinely useful behavioral fact beyond annotations: '1 point per returned record,' a cost disclosure. It does not cover return format or pagination, so it is adequate but not rich.

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, zero waste, and the core content (products plus recommender) is front-loaded before the cost note. Nothing could be cut without losing 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 two-parameter read tool with no output schema, the description covers what is returned (products + recommenders) and the billing model, while annotations carry the safety profile and the schema carries parameter details. Only pagination/return-shape specifics are absent, a minor gap.

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 both parameters (user, max_items with its 250 cap and default of 25) are fully documented in the schema. The description adds only that the lookup is scoped to a user's stack, which is implied by the required user param. 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?

The description states a specific verb+resource: retrieving products in a Product Hunt user's 'stack' along with recommender attribution. 'Stack' is a distinct resource that separates it from siblings like users_collections, users_upvotes, and users_launches. It does not explicitly name those siblings, but the resource itself is unambiguous.

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?

There is no when-to-use guidance, no prerequisites, and no mention of alternatives such as run_producthunt_users or run_producthunt_users_collections. The agent must infer from the name alone that this is the tool for stack data.

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