open-context

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

No annotations provided, so description carries full burden. While it mentions 'cache' implying side effects, it fails to disclose what is cached, cache duration/invalidation rules, rate limits from GitHub, or what specific information is returned (URLs, changelogs, metadata).

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 sentence with no waste. Efficiently front-loads the core action and subject, though slightly more detail on return values could improve utility without sacrificing brevity.

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?

Lacks output schema and provides no description of return values or data structure. The term 'information' is vague regarding what specific Jenkins release data (URLs, checksums, release notes) is retrieved. Missing cache behavior details expected for a caching 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?

With 100% schema description coverage for the single 'version' parameter, the schema adequately documents input requirements. The description adds no parameter semantics, meeting the baseline for high-coverage schemas.

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 identifies the action ('Fetch and cache'), resource ('Jenkins versions'), and source ('GitHub releases'), distinguishing it from sibling info-getters by specifying the Jenkins domain and GitHub-specific origin.

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?

No guidance provided on when to invoke this tool versus siblings like open-context_get_docs or version-specific alternatives, nor any mention of prerequisites or constraints.

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