Api integrations test connection create

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

Annotations already disclose that this is not read-only, is open-world, non-idempotent, and non-destructive. The description adds the important behavioral detail that nothing is saved, which is valuable beyond the annotations. It still does not describe what the test does externally or what the result indicates.

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 a single efficient sentence with the key constraint front-loaded. 'An endpoint to' is slightly redundant, but the sentence contains no substantive waste.

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?

For a zero-parameter operation with annotations covering safety and openness, the description gives adequate high-level context. However, it does not explain how credentials are supplied despite the empty schema, nor what a successful or failed test returns, leaving some ambiguity for an agent.

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 and 100% schema description coverage, so there are no parameter semantics for the description to explain. The baseline for zero-parameter tools 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 names a specific verb and resource: test connection credentials. It also states a key scope constraint, 'without saving them,' making the operation distinguishable from a create/save flow. It does not explicitly distinguish itself from the sibling `integrations_configs_test_connection_create`, so it stops short of a 5.

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 phrase 'test connection credentials without saving them' implies the intended use case: validating credentials before persisting them. However, it gives no explicit guidance on when to use this tool versus the sibling configs test-connection tool, nor any prerequisites or exclusions.

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