Test connection

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

With no annotations, the description carries the full burden of behavior disclosure. It explicitly states the operation is read-only and that the seller account is not modified, which is strong side-effect transparency. It does not mention failure behavior or permissions, but the core safety profile is clearly conveyed.

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 sentence that front-loads the central action ('Performs a real read-only connectivity check') and then appends the key scoping detail. There is no filler or redundant restatement of the tool name.

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 one-parameter tool, the description covers purpose and side-effect safety, but omits the return/response shape and never explains connection_id origin. Since there is no output schema, this is a non-trivial gap for an agent deciding whether the call succeeded.

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 property, connection_id, is not explained in the description. An agent must infer that it identifies the connection to test; no guidance is given about where to obtain it or how it relates to other connection tools.

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 identifies a specific operation — a 'real read-only connectivity check' — and names what it verifies: token validity and API availability. It doesn't explicitly differentiate from siblings like connection_get, but the test-vs-get distinction is implied.

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?

No when-to-use or alternative-selection guidance is provided. An agent is not told to use this tool before other connection/API tools or when credentials need validation, so it must infer applicability from the title and purpose.

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