Integrations: test

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

Annotations declare readOnlyHint=false, destructiveHint=false, and openWorldHint=false, but the description adds nothing beyond them. It does not say whether testing performs a live external call, whether it mutates connection state or health status, or whether failures are reported as errors or as a status value.

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 two-word phrase is not padded, but it is under-specified rather than concise: it front-loads nothing useful and leaves no structure for an agent to act on beyond the literal words.

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?

No output schema exists, so the description should explain what the test returns (success/failure, diagnostics, latency); it says nothing. For a tool whose only value is the result of a check, this is a meaningful omission.

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 100% for the single connection_id parameter, so the schema carries the parameter documentation. The description adds no format, source, or constraint detail (e.g., where to obtain the connection ID), so the baseline of 3 applies.

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 gives a verb and a resource ("Test a connection"), so the general purpose is inferable, but it is vague about what "test" means — credential validation, reachability, latency? It also does not distinguish this tool from siblings such as integrations_connect, integrations_get, or integrations_connections_list.

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 call this versus alternatives like integrations_get or integrations_connections_list, and no statement of prerequisites (e.g., that the connection must already exist via integrations_connect). The agent is left to infer usage entirely.

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