list_businesses

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

With no annotations, the description carries the full burden. The verb 'List' implies a read-only, non-mutating operation, and the description explicitly states what information is returned (payout wallet addresses and domain verification status). It does not mention pagination or rate limits, but those are less critical for a no-arg list endpoint.

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, information-dense sentence. It front-loads the core action and resource, then adds only the relevant output attributes. No filler or unnecessary detail.

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-all tool, the description gives sufficient information to invoke it correctly, including what the response will contain. Without annotations or an output schema, a bit more detail (e.g., whether all items are returned at once or paginated) could help, but the core call is fully specified.

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?

There are zero parameters, so the schema fully documents the absence of inputs. The description does not need to compensate. Baseline 4 is appropriate because no parameter explanation is needed or provided.

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 uses a specific verb 'List' with a clear resource 'business contexts' and scope 'all under the merchant account'. It also names the return content (payout wallet addresses and domain verification status), fully distinguishing it from sibling get_business or get_active_business which target a single context.

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 'all business contexts' clearly implies this tool is for enumerating the full set rather than fetching a single business. It offers no explicit exclusions or pointers to alternatives, but the scope statement gives a definitive when-to-use context.

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