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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is covered without the description. The description adds a useful boundary about what signal is and is not returned, but says nothing about failure modes, auth prerequisites, or what connectivity actually means (network vs installation token). An output schema exists, so return details need not be spelled out.

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?

A single sentence with the core purpose front-loaded and the disambiguation trailing. Every clause earns its place and there is no redundancy.

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?

With zero parameters, a rich annotation set, and an output schema, the description's remaining job is to frame the concept of 'connectivity' and exclude neighboring concepts, which it does. It is slightly thin on what a negative or failing result would indicate.

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 takes zero parameters, so the baseline is 4; there is nothing for the description to disambiguate. No syntax or scoping details are 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?

States a specific verb ('read') and a specific resource ('GitHub installation connectivity'), which is concrete enough for an agent to know this is a health/connectivity probe. The negations ('not execution status or collection freshness') sharpen the purpose against likely misreadings, though no sibling tool is named for contrast.

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 exclusions imply when this tool is appropriate (diagnosing connectivity problems) and when it is not (checking run outcomes or data freshness), but there is no positive usage statement or routing to the sibling that handles those other concerns. Usage is left to inference.

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