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

No annotations are provided, so the description carries the full burden, and it delivers: it states the tool is connectivity-only, does not return analytics data, pings all connected servers, and reports reachable/unreachable status. This fully discloses the behavior an agent needs to anticipate.

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 compact and front-loaded: the core behavior and negative scope appear in the first sentence. The USE WHEN bullets and the explicit alternative guidance earn their place without any fluff or repetition.

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 connectivity-check tool with an output schema present, the description covers everything an agent needs: what it does, what it does not do, when to use it, and when to choose a sibling instead. There is no meaningful 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, so the baseline is 4. The description does not need to document parameters and instead focuses on the tool's purpose and output behavior, which is appropriate for a no-argument status check.

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 opens with a specific verb and resource: 'Connectivity check only' and 'Pings every connected Tracklution server and reports reachable / unreachable.' It explicitly distinguishes itself from analytics tools by stating 'does NOT return any analytics data' and names the siblings it is not, so an agent can reliably tell it apart.

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 'USE WHEN' section gives two concrete scenarios: isolating network vs. data issues and confirming a newly-added server is online. It also explicitly says to skip this tool for any data question and use get_summary or get_report, providing a clear exclusion and named alternatives.

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