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

Annotations already declare the tool is read-only and idempotent, so the description doesn't need to restate that. The description adds minor value by specifying 'MCP platform and adapter' versions, but it doesn't disclose any runtime behavior (e.g., network calls, caching) beyond the obvious. No contradictions with annotations.

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 front-loads the action. Every word earns its place, and it's appropriately sized for a trivial version-check tool.

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 zero parameters, no output schema, and a straightforward purpose, the description is complete. It covers exactly what versions are reported and requires no additional context.

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 description doesn't need to explain parameter meaning. With no params, a baseline of 4 is appropriate per the rubric, and the description is clear that it takes no input.

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 uses a specific verb ('show') and resource ('MCP platform and adapter versions') that clearly identifies the tool's function. It distinguishes itself from sibling tools like 'authenticate' or 'connect' by being solely about version information.

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 implies usage by its clarity (checking version numbers), but it doesn't explicitly state when to use it versus alternatives or provide any 'when not to use' guidance. It's adequate but relies on the user inferring the context from the tool name and siblings.

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