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

Annotations already declare readOnlyHint=true and idempotentHint=true, so the agent knows it's a safe, non-mutating operation. The description adds minimal extra behavioral context, such as that it outputs version numbers, but doesn't go beyond the annotations. With annotations providing key safety traits, a 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 with no wasted words. It is front-loaded with the action 'Show' and immediately identifies the resources. Perfectly concise for a zero-parameter 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 the simplicity (zero params, no output schema), the description is adequate. It explains what the tool does, but it lacks context about what the output looks like (e.g., format, whether it's a list or a string) and why one would use it. For such a simple tool, it's minimally complete but lacks extra contextual value.

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 is empty. The description defines the purpose clearly, and there are no parameters to document. Since there are no params, a baseline of 4 is given per the rubric, which is justified.

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: showing current MCP platform and adapter versions. It specifies the resource (MCP platform and adapter) and the action (show), which is sufficient. However, it doesn't explicitly distinguish from sibling tools, but given the sibling names like authenticate, connect, marketplace, etc., the purpose is distinct enough.

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 gives no guidance on when to use this tool versus others. It doesn't mention that it's a diagnostic/informational tool to check versions, or when one might want to call it (e.g., troubleshooting compatibility). The sibling tools are unrelated in name, but explicit context would be helpful.

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