ping

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

With no annotations provided, the description carries full burden. It discloses the tool's behavior (responds with 'pong') and purpose (connectivity testing), but doesn't mention potential limitations like network timeouts, authentication requirements, or rate limits. The description is accurate but lacks operational context that would be helpful for an agent.

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 perfectly structured and concise: purpose statement first, usage guidelines second, return value third. Each sentence earns its place - the first defines what it does, the second explains when to use it, and the third specifies the return value. No wasted words or redundancy.

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 this is a zero-parameter tool with an output schema (implied by the return statement), the description provides complete context. It explains what the tool does, when to use it, and what it returns. For such a simple tool, no additional information about parameters, authentication, or complex behaviors is needed.

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 with 100% schema description coverage, so the baseline is 4. The description correctly indicates this is a 'simple' tool with no inputs needed, which aligns perfectly with the empty input schema. No additional parameter information is needed or provided.

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 ('responds with') and resource ('pong'), distinguishing it from siblings like 'echo' or 'health_check' which serve different testing purposes. It explicitly identifies this as a connectivity testing tool rather than a general-purpose echo or health monitoring tool.

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 states when to use this tool: 'for testing basic connectivity and server responsiveness.' This provides clear context about its intended use case versus alternatives like 'health_check' (which might check deeper system status) or 'echo' (which might echo input rather than test connectivity).

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