get_current_model

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

No annotations are provided. The description explains that the tool retrieves a documentation page, which implies read-only behavior. It adds context by calling it a 'shortcut tool' but does not disclose any additional behavioral traits like caching or network requirements.

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: the first states the purpose, the second gives usage advice. Every sentence is necessary and front-loaded. 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?

Given the tool has no parameters, an output schema is present (context signal), and siblings provide contrast, the description is fairly complete. It covers the tool's purpose and what to expect. Minor omission: could mention if output is HTML or text, but the output schema likely covers that.

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?

There are no parameters, and schema coverage is 100% (no params). The description adds meaning beyond the schema by explaining what the retrieved documentation page contains (model variants, capabilities, versioning).

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 it retrieves the canonical 'Gemini Models' documentation page. It uses specific verbs and resource, and distinguishes from siblings like 'search_documentation' by calling itself a 'shortcut tool'.

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 says 'Use this to fast-track finding details about available model variants...' which gives clear context for when to use. However, it does not explicitly state when not to use or mention alternatives beyond the implicit sibling tools.

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