gemini_fetch

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

With no annotations, the description provides behavioral details: TLS, TOFU validation, client certificates, gemtext parsing, and returns structured JSON for LLM. It does not mention error handling, rate limits, or redirects, but for a fetch operation this is adequate.

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 concise with a few sentences and an args section. It is front-loaded with purpose. The args section for a single parameter is slightly verbose but not wasteful.

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 one parameter and an output schema (not shown), the description covers protocol, features, and output format. Minor gaps like error handling and redirects, but overall sufficient for a simple fetch tool.

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 only parameter 'url' has 0% schema description coverage, but the description adds meaningful context: 'Full Gemini URL to fetch (e.g., gemini://gemini.circumlunar.space/)', including an example and format hint.

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 fetches Gemini content by URL, specifies the protocol, and lists features like TLS, TOFU validation, client certificates, and gemtext parsing. It distinguishes from siblings (gemini_batch_fetch, gopher_fetch, gopher_batch_fetch) by focusing on single Gemini fetch.

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 implies usage for single Gemini URL fetch but does not explicitly state when to use or not use this tool versus alternatives like gemini_batch_fetch. No guidance on prerequisites or exclusions.

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