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

Annotations provide readOnlyHint=true, idempotentHint=true, destructiveHint=false, which already convey the safe, non-destructive nature. The description adds that it shows versions, but it doesn't disclose additional behavioral aspects like whether it requires authentication or affects state, which are not necessary given the simplicity. With high annotation coverage, 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 concise sentence that is front-loaded and states exactly what the tool does. There is no waste or unnecessary detail, making it highly efficient.

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 (0 params, no output schema), the description is complete enough. It covers the essential purpose and the tool has no complex behavior. The annotations provide additional safety context. Slight lack of detail on the format of the version output, but for a simple query tool, this is acceptable.

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 schema is fully covered (100% coverage). The description effectively explains what the tool does, and there's no additional parameter semantics needed. Baseline for 0 params is 4, which fits 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 tool's purpose: to show the current MCP platform and adapter versions. It is specific with a verb and resource (show versions), and while siblings like 'toolkit_info' or 'connect' may implicitly relate, the description clearly distinguishes by focusing on version display.

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 a clear context (when to use: to show version info) but does not explicitly state when not to use it or mention alternatives. Since it's a simple query tool with no parameters, usage is straightforward, though no explicit exclusions or alternative references are provided.

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