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

Annotations already declare readOnlyHint=true and destructiveHint=false, and the description's use of 'Show' aligns with a safe read operation, so there is no contradiction. Below that annotation baseline, the description only adds 'adapter versions' detail—useful info about scope but not deeper behavioral disclosure (e.g., network calls, performance). Acceptable for such a simple tool, hence a neutral 3.

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?

A single, eminently readable sentence front-loads the verb 'Show' and packs information efficiently. Every word serves a purpose without redundancy. Could not be more concise.

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 version-inspection tool with zero params, a simple description is appropriate and complete - there are no complex dependencies or return values (no output schema) that would require more elaboration. One could quibble about not documenting whether this requires an active connection (given the sibling 'connect' tool), but that is far outside the typical scope of a version check.

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?

Zero parameters exist in the schema (100% coverage trivially). With no params to describe, the baseline of 4 applies - the description isn't expected to explain inputs that don't exist. No deduction needed here.

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?

Clear verb + resource: 'Show' + 'current MCP platform and adapter versions' leaves no ambiguity about what the tool does. The scope is explicit, and despite being alongside potentially similar-sounding tools, the specific mention of versions makes it distinguishable. Nothing misleading or vague.

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 usage is implied via the description ('Show the current MCP platform and adapter versions'). Given the tool has zero parameters and a trivial return, explicit when-to-use guidance is less critical. However, no explicit mention of when not to use it or alternatives is given, placing it at baseline for a tool of this simplicity.

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