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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description itself adds no additional behavioral detail beyond what the annotations state (e.g., no mention of return format or whether network activity occurs). It doesn't contradict annotations, and given the trivial nature of the operation, 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, front-loaded sentence with no filler. Every word contributes to the purpose. It's perfectly concise for the tool's simplicity.

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 tool with no parameters and no output schema, the description adequately covers the purpose. It could mention what format the version info is returned in, but given the simplicity and the existence of annotations, it's sufficiently complete. A slight gap is the lack of any note about when the tool might fail or what it actually returns, but that's minor.

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?

There are zero parameters, and the schema fully covers this with no required fields. The description adds no parameter details because none exist. Per the rubric, baseline for 0 params is 4, and there's no deficit 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 a specific action ('Show') and the exact resource ('current MCP platform and adapter versions'). It is concise and unambiguous, and while it doesn't explicitly differentiate from all siblings, the specific mention of 'versions' makes its purpose clear enough to stand on its own.

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 alternatives such as 'toolkit_info' or 'connect'. There is no mention of prerequisites, common use cases, or exclusions. For a simple version check, this may be acceptable, but still minimal that the tool's purpose is obvious.

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