centrex_list_contacts

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

With no annotations, the description only says it supports filtering but omits key behaviors like default sorting, pagination limits, read-only nature, or what happens with no filters. Minimal disclosure beyond basic purpose.

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?

A single sentence efficiently conveys the core purpose and lists main filters, with no redundant words. However, it could be slightly better structured by separating the filter list.

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 list tool with 6 optional parameters and no output schema or annotations, the description lacks details on default behavior, pagination (offset/limit described in schema but not in description), maximum results, or returned fields. Incomplete for agents to anticipate results.

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 covers all 6 parameters with descriptions. The description adds general filtering context but mentions 'name' as a filter, which is not a separate parameter (likely part of 'search'), causing slight ambiguity. The baseline is 3 due to full schema coverage.

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 clearly states it searches and lists contacts in Centrex CRM, which distinguishes it from sibling tools like centrex_get_contact (single contact) and centrex_create_contact (creation).

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 using this tool for searching and listing contacts, but does not specify when to use alternatives (e.g., centrex_get_contact for a single known contact) or provide explicit when-not guidance.

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