set_evolution_webhook

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

With no annotations, the description must fully disclose behavior. It only states 'Configure,' implying a write operation, but does not mention side effects (e.g., overwriting existing webhook), required permissions, or whether the operation is idempotent. The lack of detail fails to compensate for absent 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 a single sentence, concise and front-loaded. It conveys essential purpose without extraneous words. However, it could include a bit more context without becoming verbose, so a score of 4 is appropriate.

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 6 parameters, no output schema, and no annotations, the description is insufficiently complete. It omits required field hints, behavior when 'enabled' is false, and what the response looks like. More detail is needed for adequate contextual completeness.

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 high (83% of parameters have descriptions in the schema), achieving the baseline of 3. The description adds no additional parameter information beyond what the schema provides, so it meets but does not exceed expectations.

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: 'Configure the webhook of an instance (where Evolution POSTs events).' It uses a specific verb ('configure') and identifies the resource ('webhook of an instance'). The parenthetical explanation adds context about the webhook's role, distinguishing it from other tools like 'get_evolution_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?

No guidance is provided on when to use this tool versus alternatives, such as when to use 'get_evolution_webhook' for reading. There are no prerequisites, exclusions, or notes on typical use cases, leaving the agent to infer context from sibling tool names alone.

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