Créer un contrat

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

The description only states the core action of creating a contract, which aligns with the annotations (readOnlyHint false). However, it does not disclose any side effects, requirements (e.g., existing resource), or error conditions, leaving the agent without important behavioral context.

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 with no redundant information, making it easy to parse. It is appropriately brief for the tool's straightforward purpose.

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?

Despite the schema covering parameters, the description lacks critical context about required fields in practice (e.g., resourceId), the return value (no output schema), and how this fits into the broader BoondManager workflow. The tool has 5 optional-looking parameters, which may mislead the agent.

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 already provides descriptions for all 5 parameters (100% coverage). The tool description adds no additional meaning about parameter usage, such as which parameters are typically required or how they interact. 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 tool creates a new employment contract in BoondManager, using the specific verb 'Crée' and the resource 'contrat de travail'. This distinguishes it from related tools like boond_contracts_get, which retrieves contracts.

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 provides no guidance on when to use this tool versus alternatives, such as boond_contracts_get for reading contracts or other create tools for different entities. There is no mention of prerequisites or situations where this tool is appropriate.

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