Créer une absence

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

The description only states that it creates an absence request, providing no additional behavioral context such as side effects, permissions needed, or state changes. Annotations are mostly false and do not supplement; thus the description carries the burden but fails to disclose important traits.

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 sentence, concise and to the point. However, it lacks structure such as bullet points or front-loading of key information. Still, it does not include unnecessary words.

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 6 parameters, 4 required, and no output schema, the description is too brief. It does not explain the return value, error conditions, or any prerequisites. Completeness is lacking for a creation endpoint.

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 has 100% coverage with descriptions for all 6 parameters. The description adds no extra meaning beyond the schema fields. For example, it does not clarify the 'state' values or 'note' format. 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 'Crée une nouvelle demande d'absence' (Creates a new absence request), indicating the verb and resource. It distinguishes from siblings like boond_absences_delete, boond_absences_get, etc. However, it does not detail what 'absence' specifically entails (e.g., types of absences).

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?

No guidance on when to use this tool versus alternatives such as boond_absences_update or boond_planning_absences_search. The description lacks context for selecting this tool over siblings.

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