Verify the bridge and hub are reachable

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

Annotations already declare readOnlyHint, openWorldHint and idempotentHint, so the bar is lower; the description still adds real behavioral detail by naming the two layers probed, the conditional hub fetch, and that it reports the failing layer plus remediation. The trailing 'Read-only' restates readOnlyHint, which is unnecessary but harmless.

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?

Three short sentences with zero waste, front-loading what is checked before how failures are reported. Every clause carries information.

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?

There is no output schema, so the description carries the burden of describing returns; it does so partially by saying it reports the failing layer and what to do about it, but does not indicate the response shape or how success is signaled. Adequate for a no-arg diagnostic, though not exhaustive.

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 there is nothing for the description to disambiguate; the baseline of 4 applies. No misleading hints about inputs are present.

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+resource (checks the bridge connection, fetches a hub's appointments page) and clearly positions itself as a two-layer diagnostic, which cleanly distinguishes it from the sibling list_* tools. The conditional 'if a hub is configured' also conveys scope precisely.

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?

Usage is implied by the diagnostic framing rather than stated: an agent can infer this is the connectivity-verification tool, but the description never says when to reach for it versus the sibling list_* tools (e.g. 'run this first if a list call fails'). No exclusions or prerequisites are given.

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