consult_gemini_oneshot

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

The description adds context about statelessness and retry logic beyond the readOnlyHint and openWorldHint annotations. However, it does not detail what happens on failure or idempotency guarantees, keeping it from a perfect score.

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 plus a line break, elegantly front-loading the core stateless concept and usage context with no wasted words.

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 tool with 9 parameters, robust schema, and annotations, the description is mostly complete. It lacks mention of the return format (no output schema), but the statelessness and usage guidance are well-covered, earning a 4.

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?

With 100% schema description coverage, the schema already documents all parameters. The description does not add extra meaning beyond what the schema provides, meeting the baseline for a 3.

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 states 'Stateless single-shot Gemini query with no session history,' which clearly identifies the tool's purpose and distinguishes it from the sibling 'consult_gemini' that likely maintains session state.

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 advises using the tool for 'independent questions, one-off lookups, or batch-style queries where conversation context would be noise,' providing clear guidance on when to use it versus alternatives.

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