Créer un(e) société

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

Annotations indicate readOnlyHint=false, confirming a write operation, and the description aligns with this by saying 'Crée'. The description adds the return behavior (data with ID), but provides no additional context on side effects, required permissions, or edge cases. It does not contradict the annotations, but it does not enrich them significantly.

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 extremely concise: two short sentences that immediately state the action and the return value. It is front-loaded and contains no redundant information, making it easy for an agent to parse quickly.

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 tool has 9 parameters and an output schema, the description is minimally sufficient but lacks contextual guidance such as which fields are required or any business rules around company creation. The input schema covers required fields, but the description does not reinforce or explain them, leaving the agent to rely entirely on schema and annotations.

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%, with each parameter having a basic label (e.g., 'Ville', 'Nom de la société'). The description does not add further meaning to the parameters beyond what the schema already provides, so the baseline of 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 tool's action: 'Crée un(e) nouvel(le) société dans BoondManager' (creates a new company in BoondManager). It uses a specific verb ('Crée') and resource ('société'), and explicitly mentions the return of the created entity with its ID, which distinguishes it from sibling tools like search, get, update, or delete.

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 company but provides no explicit guidance on when to use this tool versus alternatives (e.g., update for existing companies). No conditions, prerequisites, or exclusions are stated, leaving the agent to infer context from the tool's name and basic action.

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