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

Annotations already declare this as a safe, read-only, idempotent operation (readOnlyHint: true, idempotentHint: true, destructiveHint: false). The description adds the detail that it shows 'current' versions, implying a live system query, but provides no additional behavioral context beyond that. The description does not contradict the annotations, and the bar is lower with annotations present, but it still doesn't significantly extend them.

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 entire description is one concise sentence that is immediately understandable and front-loaded with the action ('Show'). There is zero wasted wording or redundant information, making it a model of conciseness.

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's simplicity—no parameters, no output schema, and clear annotations—the description is complete. It fully covers what an agent needs to know to use the tool, and no additional details about return values or behavior are necessary for this low-complexity 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 zero parameters, so the parameter semantics are trivially satisfied. The description confirms that no input is needed to get the version info, which is consistent with the empty schema. As per the rubric, this gives a baseline 4, since there are no parameter details to elaborate on.

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 the specific verb 'show' and identifies the resource as 'current MCP platform and adapter versions,' clearly stating exactly what the tool does. It distinguishes itself from siblings by specifying the exact type of version information returned, making it 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?

The description implies usage by stating what the tool does but provides no explicit guidance on when to use this tool over alternatives like 'toolkit_info' or 'connect'. There is no mention of exclusions or alternative tools, so the usage context is only implied, not explicitly stated.

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