Get 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 pagination behavior (meta.cursor null means end of list) and the exact-match constraint on email filtering. Being a read operation, these details cover the main behavioral traits, though it stops short of mentioning auth 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?

The description is well-structured: an opening summary, a pagination explanation, and clear Args/Returns sections. Every sentence adds value without redundancy, making it effective and easy to scan.

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?

Given no output schema, the description explains the return type as a dictionary with contacts and pagination metadata, and covers pagination flow. It lacks a detailed shape of individual contacts, but for a list endpoint this is acceptable, especially with sibling get_contact_details likely providing detail.

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?

With schema description coverage at 0%, the description fully compensates by explaining both parameters in an Args section: cursor is the pagination token from the previous response, and email is a valid full email filter. This adds meaning beyond the bare 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 tool's function: 'Get all contacts from Tidio' and defines what contacts are. It distinguishes itself from siblings like get_contact_details by explicitly covering the full list rather than a single contact.

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?

Provides clear usage context for pagination (cursor handling) and email filtering, including a note that email must be a full valid address with no wildcards. However, it does not explicitly mention when to prefer this over alternatives like get_contact_details.

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