Rechercher des webhooks

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true, so the description does not need to repeat safety. It adds value by describing the return type (list with ID, name, and main details), which is not in annotations. However, it omits details like authentication or rate limits.

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 with a single paragraph and a parameter list. However, the error in parameter defaults undermines its efficiency. It could be restructured to avoid repetition and ensure accuracy.

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 annotations and the presence of an output description (though no formal output schema), the description is fairly complete for a search tool. However, the error in pageSize limits its completeness, and it does not mention search behavior like case sensitivity or partial matching.

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 description adds some semantic value by explaining the 'keywords' parameter and noting default values, but it contains an error: it states pageSize default is 20 and max 100, while the schema specifies default 30 and max 500. This inconsistency reduces trust and usability.

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 webhooks in BoondManager by keywords with pagination. It uses specific verbs and resource names, and it distinguishes from sibling tools like 'boond_webhooks_get' which retrieves a single webhook.

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 what the tool does and lists parameters, but it does not explicitly guide when to use this search tool versus alternatives like 'boond_webhooks_get'. The usage context is implied but not explicitly stated.

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