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

The description accurately reflects the read-only behavior, consistent with the readOnlyHint annotation. It does not add extra behavioral detail (e.g., no side effects, no permissions), but given the simple nature of the action, the annotation covers the key transparency aspect.

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 fully captures the tool's purpose with no redundant words or structural complexity.

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 absence of parameters and the straightforward nature of the action, the description provides sufficient context for an agent to invoke the tool correctly. No additional details about return values or side effects are necessary.

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, and the baseline for such cases is 4. No parameter descriptions are needed, and the description does not imply any hidden parameters.

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 verb 'Show' clearly indicates a read-only informational action, and the resource is precisely specified as 'current MCP platform and adapter versions'. It distinguishes from siblings like 'toolkit_info' which might cover broader details.

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 states what the tool does but does not provide explicit guidance on when to use it versus alternatives like 'toolkit_info'. However, the purpose is simple enough that usage is likely obvious without further instruction.

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