ping

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

With no annotations, the description carries the full burden. It discloses that this is a non-mutating check (via 'kontrol' = check) and that 'ready' is not required. However, it does not mention what the response looks like, whether errors are thrown when the daemon is unreachable, or any side effects like network calls. This leaves some behavioral ambiguity.

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 two short sentences, front-loaded with the primary purpose and an important usage caveat. Every word earns its place, and it is appropriately sized for a simple health-check 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 simple ping tool with minimal parameters, the description is mostly adequate: it states what the tool does and a key usage condition. However, the absence of any return value or failure indication is a notable gap, especially since there is no output schema to fill that in. Overall, it is acceptable but not rich.

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 has two optional parameters: request_id (described as trace ID) and idempotency_key (no description). The tool description mentions neither parameter, so it adds no meaning beyond the schema. With only 50% schema coverage, the description should have at least clarified idempotency_key's purpose or stated that both are optional tracing aids, but it did not.

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 a specific verb and resource: 'connection and liveness check with daemon.' It distinguishes the tool from all trading-related siblings, as no other tool serves a health-check purpose. The note about 'ready' not required further clarifies its unique role.

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 provides clear usage context by stating that no 'ready' is required for the tool call, which tells the agent when it can be used (e.g., before the system is fully ready). However, it does not explicitly name alternatives like get_readiness, so it falls short of a full when/when-not comparison.

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