list_customers_tool

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

With no annotations provided, the description itself must carry behavioral information. It conveys that this is a listing operation, that status can be omitted for all customers, and that limit caps the result size. It does not mention sorting, pagination beyond limit, access/auth expectations, or any side effects—though 'List' implies a read-only operation.

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?

Main action and optionality are stated in one line, followed by a compact Args block covering both parameters. No filler, and the important 'omit for all customers' behavior is included.

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 two-parameter surface is simple and the output schema covers return shape, so the description documents what an agent needs for basic use. It lacks sorting/pagination semantics beyond limit and does not compare with sibling retrieval tools, but those gaps are minor for this tool.

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 has no descriptions, so the description takes the full burden and succeeds: it defines 'active'/'inactive' values for status, explains that omitting status returns all customers, and specifies limit as the maximum result count.

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 the action ('List customers') and the optional status filter clearly. It is distinguishable from get_customer_tool by the plural list/resource framing, though it does not explicitly contrast itself with any sibling tool.

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 explains the parameters but gives no guidance about when to prefer this tool over alternatives like get_customer_tool or create_customer_tool. Context like 'use this for the full customer list' or 'use get_customer_tool for one customer' is missing.

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