open-context

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

No annotations provided, so description carries full burden. Adds valuable behavioral context by mentioning 'cache' (side effect) and source 'nodejs.org' (external dependency). However, lacks details on return format, error behavior for invalid versions, or cache expiration.

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 with action verbs front-loaded. Zero redundancy. Minor deduction because 'information' is vague—could specify 'release data, changelog, or LTS status' to justify the sentence's existence given no output schema.

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?

Low complexity (1 param, no nested objects) and no output schema. Description covers basic operation but should specify what information is returned (e.g., release dates, security status, LTS flags) since there's no output schema to document return values.

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 has 100% description coverage with clear examples ('18.17.0', 'v20.0.0'). Description adds no explicit parameter guidance, but baseline 3 is appropriate since schema fully documents the single version parameter.

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?

Excellent specificity: 'Fetch and cache' are concrete verbs, 'Node.js versions' clearly identifies the resource, and 'from nodejs.org' specifies the source. Distinct from siblings like get_npm_info (packages) and get_nextjs_info (framework).

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?

Implies usage through specificity (Node.js runtime vs npm packages), but provides no explicit when-to-use guidance or differentiation from sibling tools like get_npm_info that might also return version data.

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