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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description adds the underlying endpoint (GET /customers) and hints at the returned fields, but says nothing about pagination behavior, rate limits, or result ordering beyond what the schema's page/next_page note implies.

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 short sentences with zero filler; the capability statement is front-loaded and the endpoint reference is a compact trailing detail. Nothing in the text is redundant.

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 simple, read-only, fully documented list endpoint with no output schema, the description is adequate: the agent knows what it returns and how to page via the schema. The only gap is the absence of explicit routing guidance against the singular get_customer sibling.

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 100%, so page, page_size, query and customer_type are already fully documented in the schema. The description's mention of email/phone/addresses loosely maps to the free-text query parameter but adds no new syntax or constraint information, so the baseline 3 applies.

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 pair (list or search) and the resource (customers), and enumerates the data involved (email, phone, billing and shipping addresses). It implicitly separates itself from the singular sibling veeqo_get_customer, but never names or contrasts that sibling explicitly.

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 'List or search' implies browsing/querying rather than fetching one known customer, which gives an agent some routing signal. However, there is no explicit statement of when to use this instead of veeqo_get_customer, nor any note about pagination workflow or prerequisites.

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