List Contacts

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

The description adds useful behavioral details beyond the readOnlyHint and destructiveHint annotations: it returns compact summaries with slug values for subsequent detail lookup, and notes the default sort behavior. This gives agents a clear expectation of output shape and intended follow-up actions.

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?

Two concise sentences with high information density. The first sentence states the core purpose and default ordering; the second clarifies the response format and points to the alternative tool for filtered queries. No wasted words.

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 output schema and annotations, the description is adequately complete. It covers the tool's scope, response format, and when to use an alternative. It does not explicitly mention pagination, but that is already captured in the parameter schema. Slightly more detail on the include_contact_info trade-off could enhance completeness, but it is present in the schema.

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 100%, and each parameter is already well-documented. The description adds context about compact summaries and default sorting that indirectly informs parameter usage, but does not elaborate on each parameter. Baseline of 3 is appropriate given the high 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 the tool lists all contacts in the account and specifies the default sort order (most-recently updated first). It explicitly differentiates itself from search_contacts by directing filtered queries there.

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?

Provides explicit guidance: use this tool for unfiltered lists, and use search_contacts when filtering is needed. This clear alternative reference helps agents choose correctly.

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