Rechercher des demandes d'absence

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds a useful behavioral detail: 'resourceId est converti en COMP<id>', and specifies the period format YYYY-MM, but does not describe other behaviors like pagination defaults or return structure.

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 brief, well-structured with 'Args:' and 'Returns:' sections, and every line provides value without repeating the schema verbatim. It is front-loaded with the core purpose and then lists parameter details efficiently.

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 tool is relatively simple with 7 optional parameters and no required ones. The description covers the overall purpose, mentions the key filter dimensions, and summarizes the return value. With strong annotations and complete schema descriptions, the definition is adequate, though a bit more detail on the return format could be beneficial.

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%, giving a baseline of 3. The description adds meaning beyond the schema with the conversion rule 'resourceId est converti en COMP<id>', which is not present in the parameter descriptions. This is a meaningful addition that helps the agent understand how to use the resourceId parameter.

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 states 'Recherche des demandes d'absence dans BoondManager' with a specific verb ('Recherche') and a clear resource ('demandes d'absence'). It distinguishes from sibling tools like boond_absences_get or boond_absences_create by signaling a search operation with filter criteria.

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?

Usage is implied through the verb 'Recherche' and the list of filter parameters, but there is no explicit guidance on when to use this tool versus alternatives such as boond_absences_get or boond_planning_absences_search. No exclusions or alternative tool names are mentioned.

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