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

Discloses the risk score range, four factors, and the behavior when version is omitted (highest-risk release). Without annotations, the description provides sufficient behavioral context, though it does not mention return format or side effects.

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?

Three concise sentences with no wasted words; front-loaded with the core purpose and key 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?

The description is complete for a simple tool with two parameters, covering purpose, behavior, and usage. Lacks explicit output format, but can be inferred from the score range description.

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 descriptions, but the tool description adds value by explaining the effect of omitting version and giving an example for product, exceeding the baseline of 3.

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 states the tool gets a proprietary risk score (0–100) with a four-factor breakdown, distinguishing it from sibling tools like check_eol and get_product_lifecycle which likely provide simpler EOL status.

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?

Explicitly advises omitting 'version' to score the highest-risk release and recommends using the tool to quantify danger of keeping a product running, but does not explicitly compare to siblings or state when not to use.

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