open-context

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

With no annotations provided, the description carries the full burden. It discloses the caching behavior and Docker Hub source, but lacks details on rate limits, authentication requirements, error conditions, or what specific 'image details' are returned.

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 front-loaded with the action verb. No redundancy or waste—every clause adds specific context (source: Docker Hub, scope: tags and details).

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?

For a simple 2-parameter lookup tool with complete schema coverage, the description adequately indicates return categories (tags, image details) despite lacking an output schema. Could specify what 'image details' entails (size, layers, digest, etc.).

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% with clear examples ('golang', '1.23.4-bookworm'), so the baseline is 3. The description mentions 'available tags' which lightly reinforces the tag parameter, but adds no syntax or format details beyond the schema.

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 provides specific verbs ('Fetch and cache') and resource ('Docker images from Docker Hub'), clearly distinguishing this from siblings like get_go_info or get_node_info by focusing specifically on Docker Hub image metadata.

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?

While the domain specificity (Docker images vs other tech) provides implicit differentiation from siblings, there is no explicit guidance on when to prefer this over related tools or prerequisites for use (e.g., public vs private images).

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