ping

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

With no annotations provided, the description carries the behavioral transparency burden. It discloses that the tool works 'without calling the API' and reveals the diagnostic purpose around API key configuration, which goes beyond mere name repetition and clarifies that this is a non-mutating health check.

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 sentences with no wasted words. The core purpose is front-loaded in the first sentence, and the second sentence delivers actionable usage context. Every sentence earns its place.

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 zero-parameter diagnostic ping, the description is sufficient: it states what the tool does, when to use it, and a key behavioral trait (no API call). It does not describe the exact result contents, but given the tool's simplicity and lack of output schema, this is not a significant gap.

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 and the schema is complete by being empty, so the baseline is 4. The description does not need to explain parameters and does not introduce any confusion about inputs.

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 states a specific verb and resource: 'Report server health and configuration status.' It also distinguishes itself from the document/docket siblings by noting it works 'without calling the API' and by focusing on API key configuration, which is clearly unrelated to searching or retrieving dockets.

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 says 'Use this first if other tools fail' and explains why: it detects the most common failure cause, missing API key configuration. This is clear when-to-use guidance, though it does not explicitly state a when-not-to-use scenario or name a specific alternative tool.

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