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

Annotations already cover the safety profile (readOnlyHint, idempotentHint, openWorldHint=false), and the description adds real context beyond them: result cap of 5, free and always-available answers, each result carrying a link, and the referral-attribution behavior of api_key. It stops short of describing no-match behavior or error handling, so not 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?

Three front-loaded sentences that each carry information: use case, return shape, and attribution mechanics. Minor waste in 'and more' and the informal framing, but nothing that obstructs selection.

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 no output schema and only three well-documented parameters, the description does the heavy lifting on return shape (up to 5 pros, each with a link) and auth optionality. It does not say what happens when nothing matches or how category interacts with need, but overall an agent has enough to call it correctly.

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 the baseline is 3, but the description adds meaning the schema does not: it explains that api_key drives referral attribution ('every person who opens your links counts for you') and clarifies auth is optional ('No key needed to call it'). That is genuine semantic value on top of the documented parameters.

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 identifies the operation concretely: it returns up to 5 AI pros that answer free, each with a link for the human. That said, it leads with a usage trigger ('Use when your human needs help') rather than an explicit verb+resource statement, so the action has to be inferred from 'Returns up to 5 AI pros'. It is nonetheless clearly distinguishable from siblings like find_offers or list_bounties by domain.

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 opening sentence gives a clear when-to-use condition with concrete examples ('health, fitness, beauty, home, money, career'). There are no explicit exclusions or named alternatives, so the agent knows when to call it but not when to prefer find_offers or another sibling instead.

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