list_customers

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

No annotations provided. Description labels the tool as 'list' and 'browse', implying read-only. However, it does not disclose pagination, sorting, or rate limits. Given the simplicity, it is minimally adequate but could be enhanced.

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 sentences: first states purpose, second explains data source, third lists filters. No redundant information, front-loaded with key action.

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 list tool with 4 optional parameters and an output schema, the description covers main functionality and source. Missing pagination details but overall adequate.

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 descriptions cover 100% of parameters. The description adds context (e.g., 'name/email/phone search' specifies the search field) but does not significantly extend beyond the schema. Baseline 3 is appropriate.

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?

Description clearly states 'List CRM customers' with optional filtering, specifying the verb and resource. It is distinct from siblings like get_customer (single) and sync_customers_from_inbox (syncing vs listing).

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 implies usage (browsing with filters) but does not explicitly state when to use this tool over alternatives or when not to use it. No mention of get_customer for specific lookups or sync for bulk data refresh.

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