ping

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

With no annotations and a one-word description, the tool's behavior is opaque. It does not disclose side effects, authentication needs, return values, or whether it's a read or write 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?

While the description is extremely concise, it is under-specified. The single word 'Echo' fails to provide essential structure or front-loaded information, making it unhelpful.

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 tool with one optional parameter and no output schema, the description is critically insufficient. It does not explain what the tool returns or how it behaves, leaving agents without necessary context.

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?

Although the single parameter 'prompt' has a schema description ('Message to echo'), the tool description adds no further meaning beyond what the schema already provides. The parameter role is left implicit.

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 'Echo' is minimal and tautological, merely restating the name 'ping' without clarifying whether it performs a network connectivity test or simply returns the input prompt. It lacks specificity about the verb and resource.

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?

No guidance is provided on when to use this tool or how it differs from sibling tools like 'agent-status' or 'timeout-test'. The description offers no context for selection.

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