Verify the bridge and hub are reachable

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

Annotations already mark it read-only, open-world, and idempotent. The description adds useful behavioral context: it conditionally fetches the appointments page only if a hub is configured, and it reports failure layer plus remediation. This goes beyond the annotations without contradicting them.

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, two sentences, with the primary function front-loaded and the behavioral caveat followed by the outcome. Every sentence adds information and there is no repetition of the title or annotations.

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?

Given there is no output schema, the description adequately covers what an agent needs: the resource checked, the conditional hub behavior, and the kind of output ('which layer failed and what to do about it'). It could be slightly more explicit about return shape, but it is sufficient for a zero-parameter healthcheck.

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 parameter documentation is not a burden on the description. The baseline of 4 applies, and the description does not need to add parameter semantics.

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 clearly names the exact resource ('fetchproxy browser bridge') and the specific action ('Checks'), and mentions the optional hub appointments page. This clearly distinguishes it from the sibling data-listing and page-reading tools.

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 intended diagnostic purpose is clear from 'Checks' and 'Reports which layer failed', so an agent can infer it is for connectivity verification. However, the description does not explicitly say when to prefer this tool over alternatives or provide any exclusions.

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