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

The annotations already declare readOnly, idempotent, and non-destructive behavior, which covers the safety profile. The description adds no new behavioral insights beyond what the annotations state (e.g., side effects, error handling). It only specifies the informational content of the output, which is not behavioral transparency, so the score is moderate.

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, succinct sentence that directly states the tool's function without redundancy or extraneous details. It is perfectly concise and well-structured for a trivial 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 that the tool has no parameters and no output schema, the description sufficiently indicates what the tool returns (the versions). This is enough for a complete understanding of the tool's purpose and output, especially in the context of sibling tools and typical 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 no parameters, so the input schema fully describes them trivially. The description does not need to add any parameter-related meaning, and none is missing. This dimension is fully satisfied.

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's function with a specific verb ('Show') and a specific object ('current MCP platform and adapter versions'). It distinguishes itself from sibling tools like 'authenticate' or 'connect' by focusing solely on version display, leaving no ambiguity about its purpose.

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 (when you need version info) but does not explicitly state when to use it versus alternatives or when not to use it. Given the simple nature of the tool and the absence of competing version-related tools, the guidance is adequate but not explicit, earning a mid-range score.

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