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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, which fully cover the safety profile. The description adds minimal extra behavioral context (e.g., that it shows 'current' versions), but does not describe return format or other nuances. It does not contradict the annotations, so a middle score 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, front-loaded sentence that conveys the essential information without any waste. It is perfectly concise and well-structured for a tool with no parameters.

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 low complexity (no parameters, no output schema, clear annotations), the description is fully complete. It tells the agent exactly what the tool does, and the annotations cover behavioral safety. There are no missing pieces that would hinder correct invocation.

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, and the schema coverage is trivially 100%. Per rubric, 0 parameters warrants a baseline of 4. The description does not need to explain parameters; it simply states the tool's purpose, which is sufficient.

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 clear verb ('Show') and specifies the resource ('current MCP platform and adapter versions'), making the tool's purpose unambiguous. It is specific enough to distinguish it from sibling tools like authenticate or connect, which have entirely different functions.

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 the tool is used when version information is needed, but it does not explicitly state when to use it versus alternatives or provide any exclusion criteria. Since the tool is trivial, the context is clear enough, but it lacks explicit guidance on when or when not to use it.

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