browse_customers

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

With no annotations, the description must indicate side effects; it does so only by using the verb 'retrieves,' implying a read operation. It adds that results can be sorted/filtered and that customer_id returns a single comprehensive profile, but it does not describe pagination, returned fields, or any prerequisites or side effects.

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 concise and front-loaded with the core purpose, followed by capabilities and the customer_id special case. There is minor redundancy between 'advanced filtering options' and 'filtering by minimum/maximum spend,' but no unnecessary filler.

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 read tool with six optional parameters and no output schema, the description gives a reasonable overview but leaves gaps: the return format is only vaguely described as 'detailed customer profiles,' and no pagination or ordering default behavior is stated. The schema covers parameters, but tool selection would benefit from sibling-distinguishing context.

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 coverage is 100%, so the schema already documents all six parameters in detail. The description adds only general context (advanced filtering, min/max spend, comprehensive detail for customer_id) without introducing new parameter semantics beyond what the schema provides.

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 action ('retrieves customer information'), the resource (customers), and notable capabilities ('spending data', 'advanced filtering options', 'sorting by multiple fields'). It does not explicitly differentiate from sibling tools like get_customer_contacts, but the mention of spending data and filtering narrows the scope clearly.

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?

No guidance is given about when to use browse_customers versus alternatives such as get_customer_contacts or browse_orders. The only usage note, 'When provided with a specific customer_id, it returns comprehensive information for that single customer,' is parameter-level rather than tool-selection guidance.

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