conduyt_list_smart_lists

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

With no annotations, the description carries the full burden; it does convey that results include contact counts, which is useful return-content context, and 'List' implies read-only. It omits pagination behavior, sorting, and any auth/rate-limit notes, so the behavioral picture is only partial.

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?

A single front-loaded sentence with the resource and the key returned attribute; nothing is redundant 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 zero-parameter, no-output-schema list tool, the description is nearly sufficient: it identifies the resource and notes contact counts are included. It could have added a hint about result size/pagination or how it differs from the smart-view listing, but nothing critical is missing.

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 tool takes zero parameters, so there are no parameter semantics to document; baseline 4 applies. The description does not need to compensate for any schema gaps.

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 all smart lists (segments)') and clarifies the synonym 'segments' plus the included contact counts. It does not differentiate itself from nearby siblings such as conduyt_get_smart_list, conduyt_get_smart_list_contacts, or the similarly named conduyt_list_smart_views, so an agent must still infer which one returns the collection.

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 when-to-use guidance, no mention of alternatives like get_smart_list or list_smart_views, and no prerequisites or pagination context. 'List all' implies a collection read, but nothing helps the agent choose between this and its siblings.

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