square_list_customers

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

With no annotations, the description must disclose behavioral traits. It mentions pagination via the 'cursor' parameter but does not state that the operation is read-only, any required permissions, or that it returns all customers (subject to pagination). The minimal description leaves significant transparency gaps.

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 short and front-loaded with a clear purpose sentence, followed by a simple args list. It contains no fluff, but it could be more structured (e.g., separate usage note). Overall, it earns its place efficiently.

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?

Given the tool's simplicity (2 optional params, output schema exists), the description covers the basic purpose and parameters. However, it lacks differentiation from sibling tools and does not explicitly state pagination behavior or the scope of results. It is minimally functional.

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%, so the description must add meaning. It provides brief but clear explanations for 'limit' (maximum customers to return) and 'cursor' (pagination cursor from previous response). However, it does not mention the default value for limit (100) or elaborate on cursor usage.

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 states 'List customers in the connected Square account,' specifying the verb (list) and resource (customers). This distinctly identifies the tool among Square siblings like square_list_payments or square_list_locations, as it is the only customer-specific list tool.

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 provided on when to use this tool versus alternatives such as square_search_catalog or other list tools. It does not specify exclusions or comparative advantages, leaving the agent to infer usage context.

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