shipstation_test_connection

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

With no annotations present, the description carries the behavioral disclosure burden. It does disclose that the operation is read-only and identifies the exact API call, which is useful. However, it does not describe what a successful probe returns, what happens on failure, or any response semantics, leaving the agent without full visibility into the tool's behavior.

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 sentence with no filler. The action, target, and read-only nature are all front-loaded, and every word adds information.

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 connection test, the description is mostly complete: it names the system, the endpoint, and the safety profile. However, because there is no output schema, the agent is not told what a successful response looks like or how to interpret the result, which is a notable gap for a test/probe tool.

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 input schema has zero parameters, so the baseline is 4 per the rubric. The description does not need to explain parameter meanings because there are none to document.

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 ('Probe'), a specific resource ('ShipStation API'), and the exact endpoint ('GET /v2/carriers'). It clearly distinguishes this tool from the other test_connection siblings by naming the target system explicitly.

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 description implies the tool is used to verify ShipStation connectivity, but it does not explicitly state when to use this over other test_connection tools or provide exclusion criteria. The sibling names suggest alternatives, but the description itself offers no direct routing guidance.

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