gemini_validate_architecture

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

With no annotations, the description must convey behavioral traits. It only states the purpose, not whether the tool modifies files, requires permissions, produces reports, or any side effects. 'Validate' implies non-mutating analysis, but details are absent.

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 a single concise sentence that is easy to parse and front-loads the primary action. It could be expanded with usage guidance, but as a minimal statement it is not verbose or redundant.

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?

The tool has multiple parameters, no output schema, and no annotations, yet the description only covers the basic purpose. It omits default behavior, expected output, and how validation_focus affects results, making it inadequate for an agent to fully understand the tool's scope.

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?

The schema provides descriptions for two of three parameters, but the description adds no parameter-level information. The validation_focus enum is self-explanatory but lacks a description; the tool description does not clarify defaults or how parameters interact.

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 clearly states the tool validates code architecture and design patterns, with a specific verb and resource. It does not explicitly distinguish itself from sibling tools like gemini_code_review or gemini_analyze_code, so it lacks sibling differentiation.

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?

No guidance is given on when to use this tool versus the sibling tools. The description only says 'Use Gemini CLI to validate code architecture and design patterns' without explaining appropriate contexts or alternatives.

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