conduyt_get_smart_list_contacts

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

With no annotations, the description carries the burden, and it does add real value by disclosing that dynamic lists execute the filter query rather than returning stored members. It omits the read-only nature, any cost/latency implication of running a dynamic filter, and pagination defaults.

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 tight sentences with the core purpose first and the static/dynamic qualification second; nothing is wasted or buried.

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 three-parameter read tool with a fully described schema and no annotations, the description covers purpose and return semantics per list type. Pagination behavior and the read-only guarantee are the only minor gaps.

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 smartListId, page, and per_page are already documented; the description adds no format or pagination guidance beyond the schema. 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?

A specific verb and resource: 'Get contacts in a smart list,' which is clearly distinct from conduyt_get_smart_list (metadata) and conduyt_list_contacts (all contacts). It does not explicitly name those siblings to route the agent away from them, keeping it 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?

Usage is only implied by the operation itself; there is no statement of when to prefer this over conduyt_list_contacts or conduyt_get_smart_list, nor any prerequisites (e.g., the list must exist). The static-vs-dynamic sentence describes behavior rather than when-to-use.

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