test_site_connection

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

No annotations are provided, so the description carries the full behavioral burden. It hints that discovery is 'read-only', which implies non-destructive, but says nothing about permissions required, whether the connectivity test has side effects or latency, failure modes, or what a probe actually exercises.

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 short sentence with no filler, and the key action and scope come first. Nothing is wasted, though there is very little to structure.

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?

An output schema exists, so return values need not be explained. Still, with no annotations the description should cover the safety/behavioral profile of a test-and-probe tool, and it leaves that almost entirely implicit.

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?

Schema description coverage is 0%, and the only parameter is a required site_id. The description's phrase 'for one site' vaguely maps to it but adds no format, source, or lookup guidance (e.g., where to obtain the id), leaving the semantic burden unmet.

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 names a specific action (Test) and a specific scope (MCP connectivity and read-only discovery for one site), so an agent can tell roughly what happens. It does not, however, differentiate against siblings like get_site or diagnose_sites, which also inspect a single site.

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 only implied: 'Test connectivity' suggests using this before relying on a site's tools, but there is no explicit when/when-not statement and no sibling is named as an alternative. The agent must infer that this is a preflight/health check.

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