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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety and open-world scope are covered. The description adds little behavioral detail beyond 'return matching records for discovery' — no mention of pagination behavior, result shape, or rate constraints. With annotations carrying the safety profile, a 3 is appropriate.

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 tight sentences with the search scope front-loaded and the routing guidance second. No filler, though the routing sentence could be marginally more compact.

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?

With a full schema (100% coverage) and an output schema present, return values need not be explained. The description is complete for invoking the tool and routing to siblings; only deeper behavioral notes (pagination, rate limits) are absent, which is 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 coverage is 100%, so all five parameters (query, type, topics, featured, page) are documented in the schema itself. The description's phrase 'products, users, or launches' loosely echoes the `type` parameter but adds no syntax or default details. Baseline 3 when the schema does the heavy lifting.

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 (search) and the resources it covers (Product Hunt products, users, or launches), and it names the sibling tools (producthunt_makers, producthunt_launches) that handle the browsing case. An agent can distinguish this from the browse-oriented siblings without opening a schema.

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?

Explicitly frames the workflow: use this to search and identify a result type, then use producthunt_makers or producthunt_launches to browse makers/launches. It gives clear context for when to reach for this tool, though it stops short of stating when-not to use it (e.g. for direct product detail lookups via producthunt_product).

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