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

With no annotations, the description carries the burden of behavioral disclosure. 'Quick connectivity test' implies a non-destructive, read-only action, but it does not explain what happens on failure, timing expectations, or any side effects. It provides minimal behavioral insight.

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 extremely concise: only four words. It is front-loaded and contains no filler. However, it is so brief that it sacrifices useful detail, though for a simple ping tool with no parameters, this level of brevity may be acceptable.

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?

The description lacks context about what the tool returns, how to interpret results, or when to use it. Given there is no output schema, the description should explain the expected outcome or response. It also does not mention any prerequisites or limitations. The tool is simple, but the description is too sparse to be fully useful.

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 already fully covers parameter documentation. Per the rubric, a baseline of 4 is appropriate. The description adds no parameter information, but none is needed.

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 purpose: 'Quick connectivity test.' It clearly indicates the tool tests connectivity and is quick, which is distinct from a generic action. However, it does not explicitly differentiate from sibling tools like health_check or freshness_check, which might also involve connectivity checks.

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 usage guidance is provided. The description does not mention when to use this tool vs alternatives, nor any exclusions. The only implication is that it is a 'quick' test, but there's no context about scenarios where this tool is preferred over others.

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