Rechercher des comptes utilisateurs

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

Annotations already provide readOnlyHint=true, etc. The description adds that it returns a list with ID, name, and main details. However, there is a discrepancy between the description and schema for pageSize (default 20 vs 30, max 100 vs 500), which could confuse agents.

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 concise (one line for purpose, then bullet list for parameters, then return). It is front-loaded and easy to parse. However, the inaccuracy in pageSize reduces its effectiveness slightly.

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 an output schema (context signal) and annotations provide safety guarantees, the description covers basic usage. But it omits details about the return structure (vague 'détails principaux') and has the pageSize inconsistency, leaving some uncertainty.

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%, so the schema already documents all parameters. The description repeats them but introduces incorrect values for pageSize (default 20, max 100 vs schema's default 30, max 500). It adds no significant meaning beyond the schema and misleads.

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 it searches for user accounts by keywords with pagination. The verb 'Rechercher' and resource 'comptes utilisateurs' are specific. However, it does not explicitly distinguish from sibling search tools like 'boond_resources_search', but the resource type is distinct.

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 explains the parameters and pagination, which implies usage for keyword-based search. However, it does not explicitly tell when to use this tool versus alternatives (e.g., boond_accounts_get for a single account). No exclusions or prerequisites are mentioned.

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