Check Connection Health

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

Annotations declare readOnlyHint=true and destructiveHint=false, so the agent already knows this is safe. The description adds the context that it validates credentials against the source system (implying an external network call), which is somewhat useful. However, it doesn't disclose whether this is an expensive/slow operation, whether it may fail due to connectivity, or what happens for invalid credentials.

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 clean sentence, no filler, no repetition of the tool name. Every word earns its place.

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 one undocumented parameter (0% schema coverage), no output schema, and no guidance on return values, failure modes, or when to use this tool, the description is minimal. It's adequate for basic comprehension but lacks the operational detail needed for an agent to reliably invoke and interpret results.

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%, so the description carries the full burden for the 'provider' parameter. The description mentions 'a connection's credentials' but doesn't clarify that 'provider' identifies which connection/system to check. It doesn't explain what values are acceptable (identifier format, system names vs. connection IDs), leaving the agent guessing about the parameter's meaning.

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 states a specific action (verify a connection's credentials against the source system) with a clear resource. It distinguishes itself from siblings like list_connections and get_connection by emphasizing a verification/health-check action rather than retrieval, though it doesn't explicitly define what success/failure looks like or what information is returned.

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?

There is no guidance on when to use this tool versus alternatives. It doesn't say that it triggers an active check against the source system (vs. returning stored state) or that it's appropriate before calling operations. No exclusions or alternatives are mentioned.

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