teamleader_contacts_list

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

No annotations are provided, so the description carries the full burden for behavioral disclosure. It does not explicitly state that the operation is read-only, describe any pagination or limits, or mention potential side effects. The filter list is also slightly inaccurate (says 'company' instead of 'company_id' and omits 'status'), reducing transparency.

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 clear sentence that front-loads the core purpose and then lists filter capabilities. No wasted words, and the structure is 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?

The description is adequate for a simple list tool with four optional parameters, but it lacks information about pagination, result ordering, or the absence of an output schema. It also fails to mention the 'status' filter, which is in the schema. Overall, it covers the essentials but leaves 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 coverage is 100%, so the baseline is 3. The description's list of filters ('name, email, company, or tags') loosely maps to the schema but omits 'status' and uses 'company' instead of 'company_id', which could mislead. It does not add meaningful parameter semantics beyond the 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 verb 'List' and the resource 'contacts from Teamleader Focus', making the core purpose obvious. It does not explicitly distinguish itself from sibling tools like teamleader_contact_info, but the plural action and filter options imply a collection query.

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 description implies use when a list of contacts is needed, and mentions filter options. However, it does not provide explicit when-to-use vs. alternatives, mention that all parameters are optional, or exclude cases where contact_info would be more appropriate.

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