Rechercher des business units

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

Annotations already declare readOnlyHint, destructiveHint, idempotentHint, and openWorldHint, so the safety profile is clear. The description adds minimal behavioral context by stating it returns a list of matching business units. However, it does not elaborate on pagination behavior or result structure beyond what the schema implies.

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 with two short sentences. The first sentence immediately states the purpose, and the second notes the return type. There is no superfluous information, earning a maximum score.

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 low complexity with three well-documented parameters and comprehensive annotations, the description is adequate but lacks explicit detail on return format (e.g., whether it returns IDs or full objects) despite the absence of an output schema. Pagination is implied by parameters but not explicitly stated.

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 coverage is 100% with descriptions for all three parameters (keywords, page, pageSize). The description does not add any parameter-specific meaning beyond the schema, so it meets the baseline without further enhancement.

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 that the tool searches for business units ('Recherche des business units'), which is a specific verb+resource. The name and title reinforce this. However, it does not explicitly differentiate from the sibling tool boond_business_units_get, though the distinction is implied by 'search' vs 'get'.

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 (e.g., boond_business_units_get) or any context about prerequisites. It simply states the action without usage scenarios or exclusions.

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