list_contacts

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

With no annotations, the description carries the transparency burden. It discloses that the tool returns name, email, phone, and lifecycle stage, which is helpful. However, it does not explain pagination behavior, ordering, or whether search is exact or fuzzy, leaving some behavioral aspects undocumented.

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 two sentences plus an example, with the core purpose front-loaded. Every sentence adds value: action, optional filtering, return fields, and concrete user prompts. 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?

For a simple list tool with all-optional parameters and no output schema, the description is fairly complete. It covers what the tool does, what it returns, and provides examples. It lacks details on pagination defaults or response structure, but the schema covers parameter behavior, making this sufficient.

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 schema covers 100% of parameters with descriptions, so the baseline is 3. The description adds minimal semantic value by marking search/filtering as optional and providing an example, but it does not enhance understanding of page or limit beyond the schema.

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 action ('List contacts in your CRM') and distinguishes it from sibling tools like get_contact, create_contact, and delete_contact. It also specifies the scope (search and filtering) and return fields (name, email, phone, lifecycle stage), making the purpose unmistakable.

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 for listing and searching contacts, with examples like 'Show my contacts' and 'Find contacts named John.' It provides clear context but does not explicitly mention when to use get_contact instead, so it lacks exclusions or alternatives.

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