teamleader_webhooks_unregister

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

With no annotations provided, the description must carry the full burden of behavioral disclosure. It simply restates the action ('Unregister a webhook URL') without detailing side effects, idempotency, error conditions, or whether the URL is removed entirely if no event types remain. No additional context is given.

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, direct sentence that front-loads the action and scope. Every word earns its place; there is no padding or redundancy.

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?

For a simple 2-parameter mutation tool with full schema coverage, the description is largely complete. It clearly states what unregistration does, but lacks explicit mention of edge cases (e.g., what happens if URL is not registered) and doesn't point to the related register tool. Minor gap given the low complexity.

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 description coverage is 100% for both parameters ('The webhook URL to unregister' and 'List of event types to unsubscribe from'), so the description adds no new meaning beyond the schema. Baseline 3 applies.

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 uses the specific verb 'Unregister' with the resource 'webhook URL' and scopes it to 'given event types'. This clearly distinguishes it from sibling tools like teamleader_webhooks_register and teamleader_webhooks_list.

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?

Usage context is implied as the inverse of registration, but there is no explicit guidance on when to use this tool versus alternatives, no exclusions, and no mention of prerequisites (e.g., URL must be currently registered). The sibling names hint at the relationship but the description does not state it.

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