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

Annotations already declare readOnlyHint and openWorldHint, so the safety profile is covered. The description adds that results are 'matching records' and that a result-type choice governs what comes back, which is useful context, but it discloses no rate limits, pagination behavior, or coverage limits.

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 sentences with the core action front-loaded and no filler. It is tight, though the second sentence is slightly vague about which detail tool to fetch from.

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?

An output schema exists, so return values need not be described. For a read-only search tool the description is largely sufficient, though it could better distinguish this endpoint from the sibling producthunt_makers/launches/product tools it overlaps with.

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 documents all five parameters. The description adds a bit of meaning to the `type` parameter ('choose the appropriate result type'), but contributes nothing about `topics`, `featured`, or `page` beyond what the schema already states, so the baseline 3 holds.

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 (Search) and resource (Product Hunt products, users, or launches) plus the required query input. It distinguishes itself as the discovery entry point but does not name specific siblings like producthunt_makers or producthunt_launches that also return these entities.

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 phrase 'choose the appropriate result type to discover a product or maker before fetching its detail' implies the intended workflow (search first, then fetch detail), but it never names the detail tools or states when to prefer producthunt_launches/makers over this search. Usage is only implied.

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