List connected accounts

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

There are no annotations, so the description carries the burden of behavioral disclosure. It does add context beyond the title by naming the platform scope and the status fields returned, but it does not describe pagination, return shape, whether only summary fields are included, or any rate-limit/auth considerations.

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 one sentence, front-loaded with the primary action, and includes the key scope and status details without filler. Every phrase contributes useful 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 low-complexity list tool with a single optional parameter, the description covers the core behavior and the returned status categories. However, with no output schema and no annotations, it leaves out return-format details, pagination behavior, and any mention of limitations, so it is adequate but not fully complete.

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 schema has one optional 'limit' parameter with default, min, and max, but the description provides no parameter context. Since schema description coverage is 0%, the description does not compensate for the missing parameter semantics, though the single parameter is simple and self-explanatory.

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 verb and resource: 'List the connected accounts of this Stripe Connect platform.' It also clarifies the returned information ('status (charges, payouts, requirements due)'), which differentiates it from singular-account siblings like stripe_get_account and diagnostic tools like stripe_diagnose_account.

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 guidance is given about when to use this tool versus stripe_get_account, stripe_diagnose_account, or other list tools. The intended use is only implied by the verb 'list' and the resource name; there are no explicit exclusions or alternative recommendations.

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