teamleader_create_contact

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

No annotations are provided, so the description must carry the full disclosure burden. It only states the action 'create' without revealing what the tool returns on success, error behavior, idempotency, prerequisites, or any side effects. This is a notable gap for a mutation tool.

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 a single, concise sentence that is front-loaded with the core purpose. It contains no filler or redundant wording, making it appropriately sized for the tool's simplicity.

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 schema richly documents all parameters, but with no output schema and no annotations, the description lacks essential behavioral context such as return value or success indicators. It is adequate for basic tool selection but insufficient for fully informed invocation without additional assumptions.

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 input schema provides detailed descriptions for all 8 parameters, achieving 100% coverage. The tool description itself adds no parameter-level information beyond the schema, so it does not enhance what the schema already offers.

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 'Create', the resource 'contact', and the system 'Teamleader Focus', making the tool's purpose unambiguous. It also distinguishes it from sibling tools like teamleader_update_contact, teamleader_list_contacts, and teamleader_get_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?

The description implies usage: use this tool when you need to create a new contact. However, it provides no explicit guidance on when not to use it or alternatives (e.g., for adding tags separately via teamleader_contacts_add_tags), and does not mention required fields like first_name and last_name beyond what the schema already shows.

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