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

The annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, providing safety information. The description adds no additional behavioral context beyond stating what it shows. It does not contradict the annotations, but it also doesn't enrich them with extra details like return format or side effects. Given the annotation coverage, a score of 3 is appropriate.

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 purpose. Every word is necessary, with no filler or redundancy. It perfectly adheres to the principle of minimal yet complete information.

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 simple informational tool with no parameters and no output schema, the description adequately explains what the tool does. It doesn't need to elaborate on return values because 'Show' implies a simple display of versions. The tool's simplicity means the description is complete without adding superfluous detail.

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 fully covers parameter semantics (100% coverage). According to the rubric, a baseline of 4 is appropriate for zero-parameter tools. The description does not need to add parameter details since there are none, and it correctly implies the tool requires 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 clearly states the tool's purpose with a specific verb ('Show') and a clear resource ('current MCP platform and adapter versions'). It distinguishes itself from sibling tools like authenticate or connect, which serve different functions. The purpose is unambiguous and directly tied to the tool's name.

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 context is clear: this tool is for retrieving version information. It does not explicitly mention alternatives, but given its unique purpose among the siblings (authenticate, connect, etc.), there is no ambiguity about when to use it. No exclusions are needed, so the absence of when-not guidance is acceptable.

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