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

Annotations only cover readOnlyHint and openWorldHint; the description adds real behavioral context beyond them: what the response contains, the adaptive scoring criteria, the depth-2 sub-idea expansion, and the honest caveat that scores are quick model estimates not research. It does not say whether the map_url result is persisted or how it is shared, which keeps it short of 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?

One dense paragraph, roughly 110 words, front-loaded with purpose before mechanics and caveat. Every clause carries information, though the long criteria parenthetical makes it slightly run-on.

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?

No output schema exists, and the description fully covers the return surface: scored ideas sorted best-first, optional sub-ideas at depth 2, and a map_url for follow-up work. An agent has everything needed to call it correctly and describe the result.

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 baseline is 3, but the description adds meaning the schema lacks: it spells out which scoring criteria each kind of brainstorm produces and reinforces the depth-2 behavior and best-first ordering. The mode enum's individual values are left to the schema, so it does not fully compensate on every parameter.

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 and resource (brainstorm scored ideas for a topic) plus concrete scope: scored 1-10 on three criteria, overall score, sorted best first. It is immediately distinguishable from every sibling, which are all trust/check/score tools unrelated to idea generation.

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?

Usage is implied through mode examples ('for business ideas: market size...; for problem solving: impact, feasibility...') and the depth tradeoff, and the score-quality caveat steers the agent appropriately. However there is no explicit when-to-use/when-not statement and no named alternative, so the routing guidance is only inferred.

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