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

Annotations already declare readOnlyHint: true, idempotentHint: true, and destructiveHint: false, so the safety profile is fully covered. The description adds no additional behavioral context beyond that, such as what happens if versions are unavailable. It does not contradict annotations, but also provides no extra transparency value.

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, concise sentence that directly states the tool's purpose without any fluff or redundancy. It earns its place entirely and is appropriately front-loaded, making it easy for an agent to quickly grasp the function.

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 tool's simplicity—no parameters, no output schema, and strong annotations—the description fully covers everything an agent needs to know. It clearly states what the tool does, and the annotations handle safety characteristics. There are no missing elements that would impede correct usage.

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?

The tool has zero parameters, so the schema trivially covers 100% of its parameter definition. Per the rubric, a description of a tool with no parameters can rely on that baseline without needing to compensate for undocumented parameters. No additional parameter semantics are needed.

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 displays current MCP platform and adapter versions with a specific verb ('show') and resource ('versions'). This unambiguously distinguishes it from sibling tools like authenticate or report_bug, which serve entirely different functions.

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 does not explicitly state when to use this tool or any alternatives. However, the use case is implied by the tool's nature (checking versions), so an agent can reasonably infer when to invoke it. No exclusions or alternative recommendations are provided.

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