List connections

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

With no annotations, the description carries the transparency burden. It discloses that the tool is read-like ('Returns...') and explicitly guarantees no keys or secrets are exposed. Minor omissions remain, such as pagination or exact response structure, but the core behavioral scope is clear.

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?

Two tightly written sentences with no filler. The main purpose is front-loaded, the security qualifier is parenthetical, and the usage instruction is a separate clear sentence.

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 list tool with no output schema, this description is sufficient. It names the resource, the scope ('every connected marketplace seller account'), a key output field (connection_id), and how the tool fits into the broader workflow.

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 properties and is fully covered, so there are no parameters to describe. The description adds useful semantic context by explaining that the returned data contains connection_id, which is the meaningful output for downstream calls.

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?

States a precise verb and resource: it 'Returns every connected marketplace seller account.' It also clarifies what it does NOT return ('never keys or secrets'), which distinguishes it from a secrets-fetching tool and reinforces its listing role among connection_get and connection_test.

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?

Gives explicit 'when' guidance: 'Call this first to learn the connection_id required by the other tools.' It does not name specific alternatives or say when not to use it, but for a first-step discovery tool this is clear, actionable context.

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