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

The annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the agent knows this is a safe, non-destructive read operation. The description adds no further behavioral context, such as that it might require an active connection or that it returns version strings. Given the annotations cover the safety profile, the description adds minimal value; 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, clear sentence with no filler. It is appropriately front-loaded and concise, earning the highest score.

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?

The tool is simple, with no parameters, and the annotations provide safety information. However, the description lacks details on what exactly is returned (e.g., version numbers, format) and any prerequisites like an active connection. Given the simplicity, the description is adequate but could be slightly more informative about the output.

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 there is no need for parameter documentation. The schema covers 100% of parameters (none). The description doesn't need to add parameter semantics. A baseline of 4 is fair for a no-parameter tool.

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 what the tool does: it shows the current MCP platform and adapter versions. This is specific and distinct from sibling tools like authenticate, connect, or marketplace, which have different purposes. It could be slightly more explicit about the 'adapter' entity, but it's 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 provides no guidance on when to use this tool versus alternatives. It is likely a diagnostic or informational tool, but no context is given about scenarios where it would be helpful, such as debugging version mismatches or checking compatibility. Without usage hints, the agent may not know when to invoke it.

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