conduyt_export_contacts

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

No annotations are provided, so the description carries the full burden. It discloses that matching contacts are returned with tags and custom fields, but omits whether this is read-only, permission requirements, result-size limits, pagination behavior, or what 'all matching contacts' means for large exports.

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 sentences, front-loaded with the main action and output format, with no filler. The returned-fields note is useful and does not crowd out the core purpose.

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 nine-filter export tool with no output schema and no annotations, the description is minimally adequate: it names the format and some returned fields. It still lacks operational context about limits, permissions, and result shape that an agent would need before invoking an export.

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 nine filter parameters are already documented in the schema. The description adds only the general notion of filtering and does not clarify filter combination behavior or defaults, so the baseline of 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?

The description states a specific verb and resource ('Export contacts') plus output format ('as JSON') and that filtering is supported. It is clear on its own, but it does not distinguish this from sibling tools such as conduyt_export_contact_data or conduyt_list_contacts.

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 phrase 'with filtering' implies a filtered export use case, but there is no explicit guidance on when to use this tool instead of list_contacts, export_contact_data, or bulk export alternatives. No exclusions or alternative-selection conditions are given.

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