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

Annotations already declare readOnlyHint=true and idempotentHint=true, so the read-only nature is covered. The description adds no extra behavioral details beyond what annotations provide (e.g., return format). Given that annotations carry the safety profile, the description does not need to repeat it, and 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 that conveys the entire purpose without filler. It is front-loaded and wastes no words.

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 tool with no parameters, no output schema, and a trivial read-only function, the description fully satisfies the need. No additional context (like error handling) is necessary given the simplicity. The annotations cover safety, and the description covers purpose.

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 0 parameters, and schema description coverage is 100% (trivially, no properties). The baseline for zero parameters is 4; nothing is needed from the description. The description adds no parameter details because none exist.

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?

Description clearly states the tool's action: 'Show the current MCP platform and adapter versions.' The verb 'Show' plus the specific resource ('MCP platform and adapter versions') makes the purpose unambiguous and distinguishes it from siblings like connect or authenticate, which have different objectives.

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 the obvious use case—whenever version information is needed. It does not explicitly mention alternatives or exclusions, but for a simple zero-parameter version tool, this level of guidance is sufficient. No competing tool among siblings serves the same purpose.

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