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

The description does not add behavioral insights beyond what the annotations already provide (readOnlyHint, idempotentHint). It neither contradicts nor enriches the annotation information, resulting in a neutral addition.

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 sentence of eight words, front-loading the action and resource. Every word is essential, with no redundancy or filler.

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 zero parameters, no output schema, and detailed annotations, the description is fully adequate. It clearly states what the tool returns (version information) without needing further elaboration.

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 no parameters, and the input schema fully describes this. The description does not need to add parameter details; thus, it meets the baseline for zero-parameter tools.

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 shows current MCP platform and adapter versions, using a specific verb and resource. It is easily distinguishable from sibling tools, which are primarily action-oriented or domain-specific, like 'authenticate' or 'openfinance_list_accounts'.

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 a clear context for use: retrieving version information. While it does not explicitly state when not to use or suggest alternatives, the tool's simplicity and its standalone nature among siblings make the usage context sufficiently clear.

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