Rechercher des webhooks

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

Annotations already declare readOnlyHint=true, openWorldHint=true, idempotentHint=true, destructiveHint=false, covering the safety profile. The description adds the search-by-keywords scoping and pagination behavior but doesn't describe the return format details beyond 'ID, nom et détails principaux'. With strong annotations, this is acceptable but not rich.

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 compact with a clear Args section and returns line. It front-loads the purpose. Slight redundancy with schema (page/defaults repeated) but no wasted sentences overall.

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?

There's an output schema present and strong annotations, so description needn't explain returns in detail. However, the description omits the 'fields' projection parameter entirely and doesn't mention the max pageSize discrepancy — description says max 100 while schema says max 500. A search tool with pagination and projection could benefit from noting the fields mechanism.

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% — all 4 params (keywords, page, pageSize, fields) have descriptions in the schema. The description repeats keywords/page/pageSize defaults but notably omits the 'fields' projection parameter entirely. The schema does the heavy lifting, so 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 states 'Recherche des webhooks dans BoondManager par mots-clés avec pagination' — a specific verb (rechercher) + resource (webhooks) + mechanism (keywords, pagination). It distinguishes from sibling boond_webhooks_get (retrieval vs search) though it doesn't explicitly name it. Clear purpose.

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 explicit guidance on when to use this search tool vs the sibling boond_webhooks_get or other search tools. Pagination defaults are mentioned but no exclusions, prerequisites, or alternative tool recommendations are provided.

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