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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the agent knows it's safe and read-only. The description adds little beyond stating it shows versions, which is adequate for a simple read-only tool. It does not contradict annotations, so no flag.

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 one sentence with no fluff, front-loaded with the verb 'Show', and clearly conveys the purpose. Every word earns its place; it is maximally concise.

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 parameters, no output schema, but clear annotations), the description is complete enough. It covers the essential purpose without needing to describe return values or side effects. It could benefit from mentioning if it returns structured data, but that's minor.

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 coverage is 100%, so the description does not need to document parameters. With no parameters, a baseline of 4 is appropriate; the description is sufficient for a parameterless 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 it shows the current MCP platform and adapter versions, which is specific and distinct from sibling tools like authenticate, connect, and marketplace. However, it could be more explicit in distinguishing from toolkit_info, which may also provide version-like information.

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 it should be used when needing version information, but it does not explicitly state when to use it versus alternatives or when not to use it. With no parameters or context, it's straightforward but lacks explicit guidance on when it's appropriate.

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