dex_list_contacts

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions pagination and filtering capabilities but fails to describe critical behaviors like rate limits, authentication requirements, error handling, or the structure of the returned data. This leaves significant gaps for an agent to understand operational constraints.

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 efficiently structured with a clear opening sentence followed by specific examples. Each sentence adds practical value, though the examples could be slightly more concise. Overall, it's well-front-loaded and avoids unnecessary verbosity.

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?

Given the complexity (6 parameters, nested objects, no output schema, and no annotations), the description is moderately complete. It excels in explaining the 'where' parameter but neglects others and omits behavioral details. For a tool with rich filtering options, more comprehensive guidance on usage and output would be beneficial.

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 description adds substantial value beyond the schema, which has only 50% coverage. It explains the 'where' parameter with specific examples (e.g., 'where.hasBirthday', 'where.isStarred=true'), clarifying usage that isn't fully documented in the schema. However, it doesn't cover other parameters like 'take', 'skip', 'cursor', 'include', or 'select'.

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 the verb ('List') and resource ('contacts'), and mentions advanced filtering, pagination, and field selection. However, it doesn't explicitly differentiate from sibling tools like 'dex_search' or 'dex_get_contact', which might have overlapping functionality for retrieving contacts.

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 provides implied usage through examples (e.g., 'find today's birthdays'), suggesting when to use certain filters, but lacks explicit guidance on when to choose this tool over alternatives like 'dex_search' or 'dex_get_contact'. No exclusions or prerequisites are mentioned.

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