square_customers

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

The description only says 'List', implying a read operation, but offers no details about pagination, sorting, authentication requirements beyond the schema, rate limits, or the scope of data returned. With no annotations, the description fails to disclose critical 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?

The description is extremely concise, consisting of a single sentence with no extra words. However, it is too brief to be useful, bordering on under-specification rather than efficient conciseness.

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?

With five parameters, no schema descriptions, no output schema, and no annotations, the description is far from complete. It fails to explain pagination, sorting, limits, or the nature of the returned data, leaving the agent with insufficient context.

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%, meaning parameters are undocumented in both schema and description. The description adds no information about parameters like 'cursor', 'limit', 'sort_field', or 'sort_order', providing no value beyond the raw schema.

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 Square customers' with a specific verb and resource. It is immediately understandable, though it does not differentiate from sibling tools like square_catalog_list or square_payments within the description text.

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. There is no mention of prerequisites, filtering, or related tools, leaving the agent without context for appropriate invocation.

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