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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, describing a safe, non-mutating operation. The description adds the useful context that it reports current versions, which aligns with the annotations. No additional behavioral warnings or side effects are necessary for this simple version lookup.

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 sentence that fully communicates the tool's function with no filler, tautology, or redundant information. It is front-loaded and appropriately 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?

Given the tool has no parameters, no output schema, and strong annotations, the simple description fully covers what the agent needs to know: that invoking show_version retrieves current platform and adapter versions. No additional details are required for such a lightweight tool.

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 0 parameters and the schema coverage is 100%, so there is no parameter ambiguity. Per the rubric, a zero-parameter tool receives a baseline of 4; the description appropriately requires no param-level elaboration.

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 clearly identifies the resource: 'current MCP platform and adapter versions.' Among siblings like authenticate, connect, and toolkit_info, none directly overlap with version reporting, so the purpose is unambiguous.

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?

No explicit when-to-use or alternative guidance is provided. The intended usage is implied: call this tool when you need to check current platform and adapter versions. This is sufficient for a simple no-parameter tool but lacks explicit context or exclusions.

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