ping

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

With no annotations available, the description carries the behavioral disclosure burden. It clearly states the exact return format and gives a concrete example, which is strong for a simple ping tool. It does not mention failure modes or side effects, but 'Health-check' implies a non-mutating liveness probe.

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 a single sentence plus one illustrative example, with no filler. It packs the core behavior, the return format, and parameter usage into a minimal, front-loaded structure.

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 simple health-check tool with one required string parameter and an output schema, the description fully covers what an agent needs: what the tool does, what input it expects, and what output to expect. Nothing essential 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?

The schema provides no property descriptions, so the tool description must compensate. The example 'ping(message="hello") → "pong: hello"' demonstrates that the message parameter is echoed back inside the pong string, effectively conveying its semantics.

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 identifies a specific verb ('Health-check') and explicitly defines the tool's behavior: it returns 'pong: <message>'. This clearly distinguishes it from the analysis-oriented sibling 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 'Health-check' label and echo-like example make the intended use obvious, but the description does not explicitly state when to use it versus alternatives. Given that the sibling tools are clearly unrelated, the implied usage is sufficient.

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