List customer item mappings

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

No annotations are provided, so the description carries the full burden, and it discloses almost nothing: no pagination behavior despite a size parameter with a 500 max, no note about required permissions, and no indication of what the response contains. "Optional filters" is the only behavioral hint offered.

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 single sentence is short and front-loaded with no filler, which is structurally fine, but its brevity reflects under-specification rather than efficient density — the route string occupies the space where useful content should be.

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 three-parameter tool with no annotations, no output schema, and zero schema description coverage, this description is entirely inadequate. An agent cannot infer return shape, pagination, filter syntax, or how this tool relates to the many sibling list/get/upsert tools.

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 compensate for all three parameters (size, item_number, customer_number), and it does not. "Optional filters" gestures at the filter params but explains none of their semantics, the regex pattern on customer_number, or the default/max of size.

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 is essentially a restatement of the tool name and HTTP route ("GET /customer-product/list"), which is a tautology rather than an explanation of what a customer-product mapping is or what listing one returns. The only added information is "with optional filters," which hints at a list operation but does not distinguish it from siblings like list_products or get_customer.

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?

There is no stated when-to-use, no mention of alternatives such as upsert_customer_product or get_customer, and no prerequisites. "Optional filters" weakly implies a retrieval use case but gives the agent nothing to decide with.

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