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

Annotations already declare readOnlyHint=true, but the description adds the concrete endpoint (GET /customers/) and the shape of returned records, which is useful because no output schema exists. It omits any pagination or result-limit behavior, which matters for a 'list all' call.

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?

Three short sentences, front-loaded with the core purpose, followed by the field list and the usage hint. Every sentence carries distinct information, and nothing is padded.

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 listing the returned fields, and it supplies the endpoint and a discovery-oriented usage hint. The only real gap is the absence of pagination/ordering information for a potentially large listing.

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 tool takes no parameters, so there is nothing for the description to clarify beyond what the empty schema shows; baseline 4 applies. The description does not invent or misstate any input semantics.

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?

States a specific verb and resource ('List all customers') with explicit scope ('registered in your Amberflo account') and enumerates the returned fields (id, name, email, traits, enabled). The list-vs-single distinction makes it unambiguously separable from siblings like amberflo_get_customer or amberflo_create_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?

'Good first call to discover customer ids' gives clear situational context for when to reach for this tool. It does not name alternatives or state exclusions (e.g., when to prefer get_customer for a known id), so it stops short of full routing guidance.

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