get_mcp_version

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

The description discloses conditional behavior: 'If the latest version check is disabled, return only the current version. Otherwise, present the comparison URL to the user.' This goes beyond the readOnlyHint annotation by explaining what the tool returns and how it handles a specific condition, giving the agent full transparency.

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 compact and front-loaded with the core purpose, immediately followed by usage instructions. Each sentence earns its place; no redundant phrasing or filler. The conditional logic is stated succinctly.

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 no-parameter tool with an output schema, the description fully covers when to use it and what to expect as output. It explains both the default behavior and the alternative when version checking is disabled. Nothing an agent needs to invoke it correctly is missing.

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 the input schema is trivially covered. The baseline for zero parameters is 4, and the description gives no parameter-specific details because none exist. It correctly does not over-explain what isn't there.

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's function: 'Get the version of the Red Hat Insights MCP server.' The verb 'Get' and specific resource make the purpose unmistakable. It also distinguishes itself from all sibling get_* tools, none of which retrieve version 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 explicitly instructs when to call: 'Always call this if the user asks for the version... or when there is an API or authentication issue.' This provides clear contextual triggers and even covers edge cases, leaving no ambiguity about when the tool is appropriate.

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