open-context

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

No annotations are provided, so the description carries the full burden. While 'List' implies a read-only operation, the description omits return format details, pagination behavior, or whether results are cached/filterable.

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 9-word sentence that is appropriately front-loaded with the action verb 'List'. No extraneous information is present for this simple discovery tool.

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 simple schema (no parameters, no output schema), the description is minimally adequate but lacks important context. It should clarify that this returns an index/catalog needed to identify valid language/topics for use with sibling 'get_docs' or 'search_docs' tools.

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?

Input schema has zero parameters (empty object). Per rubric guidelines, zero parameters warrants a baseline score of 4 as there are no parameter semantics to clarify.

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 uses specific verb 'List' and identifies the resource as 'documentation languages and their topics', clearly indicating a catalog/discovery function. However, it does not differentiate from siblings like 'search_docs' or 'get_docs' in the open-context family.

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 provides no guidance on when to use this tool versus alternatives. Given siblings include 'search_docs' and 'get_docs', it should explicitly state this is for discovering available documentation sets before retrieval.

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