ping

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

No annotations exist, so the description carries the behavioral burden. It transparently states the exchange behavior (ping in, pong out) and the health-check purpose. It does not claim side effects or hidden behavior, which is appropriate for this trivial operation.

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 short, purposeful sentences. The first is a direct statement of behavior, and the second provides useful protocol context. No 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?

For a zero-parameter, no-output-schema health-check tool, the description is fully sufficient: it states what it does, how it behaves, and why callers use it. Nothing critical 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?

There are zero parameters and the schema already documents this fully. The description does not need to add parameter details, and adding any would be redundant.

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?

Names the exact action ('Respond to MCP ping requests with pong') and the resource/protocol involved. It is clearly distinct from all sibling registry-focused tools and adds standard-protocol context beyond simply restating the tool name.

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?

Explains that MCP proxies and clients use this to verify server aliveness. This gives a clear use context, though it does not explicitly discuss exclusions or alternatives because none are needed for a health-check ping.

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