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 covered. The description adds nothing beyond the purpose; it doesn't disclose any additional behavioral traits like output format or side effects (e.g., 'returns version strings'). With annotations present, the bar is lower, but the description still provides no extra context worth crediting.

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, efficient sentence that says exactly what is needed. Every word earns its place with no redundancy or fluff. It is ideally sized for a simple, parameterless 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?

With no output schema, the description could explain what the tool returns (e.g., version numbers or a structured list). It only says 'versions' without detail, which is adequate but not thorough. Given the simplicity and existing annotations, it is minimally complete, but mentioning the return type would raise the score.

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 input schema fully covers everything. No description of parameters is needed, and the description doesn't attempt to add anything irrelevant. The baseline of 4 for 0-parameter tools is appropriate here.

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 action ('show') and the resource ('current MCP platform and adapter versions'), which is specific and distinguishes it from sibling tools like authenticate, connect, and marketplace. It leaves no ambiguity about what the tool does.

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 states what the tool does but gives no explicit guidance on when to use it or how it differs from alternatives. There is no obvious alternative, so the context is implied, but no exclusions or prerequisites are mentioned. A more explicit 'Use this to check which version you're running' would earn a higher score.

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