open-context

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

Discloses caching behavior and external data source (GitHub), but misses critical behavioral details required without annotations: return value structure, cache duration/invalidation, rate limits, error behavior for invalid versions, and safety profile.

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?

Single efficient sentence (9 words) front-loaded with action verbs. No redundancy or extraneous text; every word earns its place.

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?

Minimal but adequate for a single-parameter read operation. Lacks output details (no output schema exists), but specifies the caching mechanism. Sufficient given low complexity, though 'information' is vague regarding what specific data is returned.

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?

Schema coverage is 100% (version parameter fully documented with examples), establishing baseline 3. Description adds no parameter context, but none is needed given complete schema documentation.

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 uses specific verbs ('Fetch and cache'), clear resource ('Kubernetes versions'), and explicit data source ('GitHub releases') that distinguishes it from siblings like get_ansible_info or get_docker_image.

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?

Specifies the domain (Kubernetes) and source (GitHub releases) which implicitly guides selection over siblings, but lacks explicit 'when to use' guidance, prerequisites, or comparisons to list_docs/search_docs alternatives.

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