listCustomers

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

No annotations are provided, so the description carries the full behavioral disclosure burden. It clearly states that this is a read-only paginated list operation and discloses the return shape: an array of customer objects with customerId, name, email, and account status. This gives meaningful behavioral transparency for a simple list tool.

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 compact, front-loaded, and every sentence contributes: the first sentence states the resource and operation, the second gives usage guidance, and the third describes the return value. There is no fluff or repetition of schema details.

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 no output schema, the description compensates by specifying the return array's fields. It also conveys pagination and usage intent. It could have explicitly guided the agent toward getCustomerDetails for single-record lookups, but the core selection and invocation context is complete.

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?

The input schema already documents both parameters (limit and status) with descriptions, defaults, ranges, and enum values, so schema coverage is 100%. The description adds little parameter-level meaning beyond labeling the result as paginated and mentioning account status in the output, which is consistent with the status parameter but not additive.

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 opens with a clear verb-resource pair ('List enterprise customer profiles') and specifies a paginated retrieval of customer accounts. It distinguishes itself from obvious siblings like getCustomerDetails by framing this tool as a browse/search/list operation, not a single-record detail lookup.

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?

It explicitly states when to use the tool: 'when you need to search, discover, or browse customer records.' It does not explicitly name alternatives or give when-not-to-use guidance, but the usage context is sufficient for an agent to distinguish it from detail, billing, and support-ticket tools.

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