consult_gemini_with_files

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

No annotations provided, but description discloses key behaviors: inline mode streams truncated snippets, at_command mode emits @path directives, and returns explanatory error string with warnings. Adequate for a query tool.

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?

Description is relatively concise with a clear intro and parameter list; no wasted sentences. Returns line adds value. Could be more front-loaded but still efficient.

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?

Given 6 parameters, no annotations, and no output schema, the description covers behavior, parameters, and return value sufficiently. Minor gap: no explicit mention of usage context beyond mode difference.

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 0% schema coverage, description compensates fully by explaining each parameter's purpose and constraints, e.g., directory resolves relative paths, mode describes two options, model lists aliases.

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?

Description specifies the verb 'send a query', the resource 'Gemini CLI', and the distinguishing feature 'with file context', clearly differentiating it from the sibling tool 'consult_gemini'.

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?

Description explains the two modes ('inline' vs 'at_command') and their behaviors, providing some guidance on how to use the tool but lacks explicit when-to-use versus siblings or when-not-to-use conditions.

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