ping

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

With no annotations, the description carries the full behavioral burden. 'Checking that the server is alive and connected' clearly conveys a read-only health check and implies no side effects. It is transparent enough for a zero-parameter ping tool, though it does not mention timeout or error behavior.

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 clear sentence with no filler or redundant wording. It front-loads the essential purpose and is appropriately sized for a trivial zero-argument tool.

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 ping/health-check tool with zero parameters and an output schema, the description provides everything needed to decide to invoke it and understand its function. No additional context is required.

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, so the schema is already complete. There is nothing for the description to add about parameters; the baseline of 4 applies because nothing is missing.

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 identifies the operation: checking that the server is alive and connected. This distinguishes it from the sibling tools, which are all contragent/debt/billing queries, so an agent can immediately recognize this as the liveness probe.

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 intended use is implied by the health-check description, but there is no explicit guidance about when to call it, when not to call it, or what to do based on the result. The sibling tools are unrelated enough that confusion is unlikely, which keeps this above 2.

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