OpenShift MCP Server

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

With no annotations provided, the description carries full burden and does well by explaining what the tool does (monitor vLLM metrics), how it works (by directly querying pods), and what it returns (markdown report). It could improve by mentioning potential limitations like permissions needed or query timeouts.

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?

Well-structured with clear sections (purpose, why, args, returns), front-loaded with the core purpose, and every sentence adds value. No redundant information or wasted 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?

Given the tool's moderate complexity (2 optional parameters), no annotations, but with output schema (returns markdown report), the description provides complete context: purpose, use cases, parameter semantics, and return format, making it fully self-contained.

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?

Schema description coverage is 0%, so the description must compensate. It fully documents both parameters (namespace and pod_filter), explaining they're optional filters and that pod_filter supports partial matching, adding significant value beyond the bare schema.

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 purpose with specific verb ('monitor') and resource ('vLLM inference server performance metrics'), and distinguishes it from siblings by specifying it queries pods directly for vLLM-specific metrics, unlike general GPU or cluster monitoring tools.

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 'Why' section explicitly lists four use cases (performance monitoring, capacity planning, resource optimization, proactive alerting), providing clear guidance on when to use this tool versus alternatives like get_gpu_utilization or get_pod_diagnostics.

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