Rechercher des webhooks

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

The description includes pagination details and a return line, but the values for pageSize (default 20, max 100) contradict the input schema (default 30, max 500). It also fails to mention the 'fields' projection parameter, providing incomplete and misleading behavioral context beyond the annotations.

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 appropriately sized and front-loaded with the purpose, but the Args section repeats schema information and introduces inaccuracies. It could be more concise and accurate by removing incorrect defaults and omissions.

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 annotated read-only operation and rich schema, the description should complement rather than contradict structured data. The pagination mismatch and missing 'fields' parameter make it incomplete and potentially misleading for an AI agent.

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?

Although schema coverage is 100%, the description inaccurately documents pageSize (default 20/max 100 vs schema's 30/500) and omits the 'fields' parameter entirely. This adds negative value by conflicting with the schema and failing to describe a valid 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 clearly states the tool's purpose: searching for webhooks in BoondManager by keywords with pagination. It uses a specific verb and resource, and the resource (webhooks) distinguishes it from sibling search tools for candidates, contacts, resources, etc.

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 implicitly indicates when to use the tool (when searching for webhooks) but does not explicitly mention alternatives or exclusions, such as using boond_webhooks_get for retrieving a specific webhook. The usage context is inferable but not clearly contrasted.

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