Rechercher des comptes utilisateurs

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint false. The description adds that it returns a list with ID, name, and details, but discloses no additional behavioral traits like authentication needs or rate limits. The conflicting pageSize limit (100 vs schema's 500) introduces a minor transparency issue.

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 has a clear summary and structured Args/Returns sections, but the Args list redundant with the schema and contains incorrect values. Not as concise as it could be.

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 description omits the 'fields' projection parameter and provides wrong pagination limits, leaving the agent with incomplete and partially incorrect contextual information. While the output schema and annotations help, the description's errors make it insufficient for fully understanding the tool's capabilities.

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 covers all four parameters, so baseline is 3. However, the description omits the 'fields' parameter entirely and provides contradictory defaults for pageSize (default 20/max 100 vs schema's default 30/max 500). This actively misleads the agent instead of adding value.

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 searches user accounts in BoondManager by keywords with pagination. The verb 'Recherche' and resource 'comptes utilisateurs' make the purpose unambiguous and distinct from siblings like boond_accounts_get, though it doesn't explicitly name alternatives.

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_accounts_get for single-account lookups. It lacks any explicit exclusions or context on preferred scenarios.

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