gemini-brainstorm

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

No annotations are provided, so the description must carry the behavioral disclosure burden. It does this well by clarifying the tool only generates ideas, produces a ranked list, and optionally includes feasibility analysis. It could go further by describing the return structure or any model-related caveats, but the key behavioral boundary—ideation only, not execution—is explicit.

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?

The description is two sentences, front-loaded with the core function, and contains no filler. The second sentence earns its place by preventing misuse through clear sibling routing.

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 9-parameter tool with no output schema, the schema covers parameters thoroughly, and the description supplies the ideation boundary and sibling alternatives. It could be slightly more complete by mentioning what the output looks like beyond 'ranked list,' but the essential context for selecting and invoking the tool is present.

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%, and each parameter already has meaningful descriptions and enums. The tool description adds high-level context about ranked output and feasibility but does not add per-parameter semantics beyond what the schema already provides. The baseline of 3 is appropriate.

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 opens with a specific verb and resource: 'Generate a ranked list of ideas for an open-ended challenge.' It names concrete creativity methods and mentions optional feasibility analysis, making the tool's function unmistakable. It also differentiates itself from siblings by explicitly saying this is ideation only, not for answers or implementation.

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 description gives explicit routing guidance: 'Ideation only: use gemini-ask for answers and gemini-plan for implementation blueprints.' This tells an agent exactly when this tool is appropriate and when to choose a sibling, leaving no ambiguity.

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