conduyt_list_contacts

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

With no annotations, the description carries the full burden. It does disclose pagination and the returned field set (name, email, phone, tags, source, assignee), which is genuinely useful since there is no output schema, but it says nothing about ordering, total-count behavior, permission requirements, or rate limits.

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 short sentences, zero filler. The purpose is front-loaded and the return-shape sentence follows immediately; every clause carries information.

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 an eight-parameter list tool with no annotations and no output schema, the description covers the essentials: filtering behavior, pagination, and the shape of returned records. Minor gaps remain around default sort order and whether total counts are returned.

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%, so all eight parameters (tag, search, source, assignedTo, masterStatus, excludeMasterStatus, page, per_page) are already documented in the schema. The description adds no parameter-level detail such as filter interaction semantics, so the baseline 3 applies.

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?

States a specific verb and resource ('List and search contacts') plus the capability ('with filtering'), so an agent knows exactly what the tool does. It does not, however, distinguish itself from siblings like conduyt_search or conduyt_list_smart_list_contacts, so it stops short of a 5.

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?

There is no statement of when to use this tool versus alternatives (e.g., conduyt_search for cross-entity lookup, conduyt_get_contact for a single record, conduyt_list_smart_list_contacts for saved segments). Usage is only implicit from the word 'filtering'.

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