Créer un(e) contact

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

The description accurately portrays the creation behavior, matching annotations (readOnlyHint=false, destructiveHint=false). It adds contextual clarity by stating it returns data with ID, but no additional traits like permission requirements are mentioned.

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: purpose and return value. Front-loaded, no waste, efficiently conveys essential information.

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 the presence of an output schema and full parameter descriptions, the description is sufficiently complete. It lacks minor details like side effects or relationships, but the overall context is clear.

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 the description adds no extra parameter meaning. Baseline 3 is appropriate.

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 'Crée' and the resource 'un(e) nouvel(le) contact dans BoondManager', distinguishing it from siblings like search, get, update, and delete. The return value is also specified.

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 for creating a new contact but offers no explicit guidance on when to use this tool versus alternatives, such as boond_contacts_update or boond_contacts_search.

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