evolution_webhook_set

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

No annotations provided; description gives no behavioral details (e.g., overwrites existing webhook, requires instance connection, validates URL). Only states 'Configure' without disclosure.

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?

Single sentence, six words – very concise, but lacks substance. It is more like a title than a functional description.

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?

With 7 parameters, nested objects, and no output schema, the description fails to explain the effect, relationship to sibling tools, or prerequisites. Extremely incomplete.

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 parameters are well-documented in the schema. The description adds no extra meaning beyond 'configure', meeting the baseline.

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 verb 'Configure' and resource 'HTTP webhook for an instance' clearly state the tool's action and target. It implicitly distinguishes from 'evolution_webhook_find' (retrieve), but no explicit differentiation.

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 on when to use this tool versus alternatives, such as 'evolution_webhook_find'. No mention of prerequisites or context like instance connectivity.

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