Connection status

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

Annotations already declare readOnlyHint, idempotentHint and openWorldHint=false, so the safety profile is covered; the description adds the diagnostic framing and the fact that it reports the MCP server's permission mode. Minor gap: it does not say what happens on connection failure (error vs. degraded status), which is the key behavioral outcome for a connectivity check.

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?

Two sentences, no filler; the payload of reported fields comes first and the usage trigger follows. Nothing is redundant with the schema or annotations.

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?

No output schema exists, so the description carries the burden of describing return values — and it does, listing the five reported facts. For a zero-parameter diagnostic tool this is sufficient to call it correctly.

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?

Zero parameters, so the baseline is 4 and no parameter explanation is required. The description correctly focuses on return content instead.

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?

States a specific verb ('check the connection') plus resource (iDRAC) and enumerates exactly what is reported: firmware, Redfish version, server model, service tag, and MCP permission mode. That reported-field list distinguishes it from generic siblings like idrac_system_overview and idrac_manager_info, which collect system or manager data rather than validating connectivity.

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?

Gives explicit usage context: 'Use this first when another tool fails or to confirm the setup works' — a clear diagnostic/first-step trigger. It does not name specific sibling tools or state when-not to use it, but the intended role is unambiguous.

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