List customers at a location

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

Annotations already establish read-only, idempotent, and non-destructive behavior, so the description need not repeat those. It adds meaningful context beyond annotations: results are grouped by customerId, guest checkouts with email now generate a customerId, and authentication is required.

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 primary behavior. The guest-checkout note is slightly tangential but still relevant to understanding the customerId grouping, and the login requirement is essential. No wasteful repetition.

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 simple read-only listing tool with an output schema and strongly descriptive annotations, the description is largely complete: it covers scope, grouping, and auth. The main omission is parameter-level detail, but the schema already encodes page/limit constraints and the optional locationId default.

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 only 33%, and the description does not compensate for the undocumented page and limit parameters. It reinforces the locationId concept but says nothing about pagination semantics or how page/limit interact.

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 'Fetch the dashboard Customers page for a location', which is a specific verb plus resource and scope. It further clarifies grouping by Crave customerId, making it easy to distinguish from the many sibling tools that deal with locations, orders, or products.

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 tool's purpose is clearly implied, and the 'Requires craveup login' line gives an important precondition. However, the description never explicitly states when to prefer this tool over alternatives or when not to use it, so usage guidance remains mostly implicit.

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