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

The readOnlyHint annotation already covers the read-only safety profile, and the description adds useful behavioral detail by naming the POST endpoint and the exact response shape, { list, next_cursor }, which is especially valuable since no output schema exists. It does not discuss rate limits or auth, but the readOnly annotation lowers the burden.

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 sentences carry the essential purpose, transport endpoint, and return shape with no filler. The list/filter action is front-loaded, and every phrase earns its place.

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?

The description plus fully documented schema gives an agent the endpoint, response shape, and pagination mechanism, which is sufficient for a read-only collection listing. It could be even stronger with an explicit pointer to get_customer for single-customer needs, but nothing essential is missing.

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%, and every parameter already has a meaningful description in the schema. The tool description adds no additional parameter semantics beyond the high-level 'filter' notion.

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 and resource: it lists and filters customers with cursor pagination. This clearly distinguishes it from singular tools like get_customer and from list tools for other resources like list_plans or list_entities.

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 description implies this tool is for listing or filtering customers and for paginated collection access, but it never explicitly says when to prefer it over get_customer or other list variants. The usage context is inferable rather than stated.

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