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

Beyond the annotations, it discloses the non-obvious cost ('1 credit') and the side effect that the call records the ask as one AI agent search, which is exactly why readOnlyHint=false and idempotentHint=false matter. It also enumerates what the summary-level response contains, so the agent knows what it gets before spending a credit.

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?

Front-loaded with the ordering cue, then purpose, return shape, cost, and a safety constraint in four tight sentences. The parenthetical list of return fields earns its space by letting the agent judge sufficiency without opening the output schema.

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 single-parameter tool with an output schema already present, the description covers purpose, entry-point role, cost, side effect, and a data-safety rule. Nothing an agent needs in order to call it correctly and safely is missing.

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% and the single query parameter already carries a length bound and an example, so the schema does the heavy lifting. The description adds a content constraint ('never send personal details or synthetic asks') but no syntax or scoping detail beyond that.

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 check ('whether people have asked for a product and could not buy it') and names the resource as 'exNiche gaps at summary level', which implicitly separates it from detail-oriented siblings like get_gap and get_dossier. It never names a sibling explicitly, so the differentiation is inferable rather than stated.

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?

'Start here' gives an explicit entry-point ordering, and 'Never send personal details or synthetic asks' is a clear when-not constraint. It stops short of naming the sibling to use for follow-up detail (get_gap/get_dossier), so the routing is left partly to inference.

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