manage_webhooks

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

No annotations provided, so description carries full disclosure burden. Adds valuable behavioral context by specifying list returns 'conditions, trigger counts, and last triggered time'. Mentions 'delete' for remove action, but omits safety details (permanent deletion, error handling, auth requirements) that annotations would typically cover.

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?

Three sentences with logical structure: overview, list details, remove details. No filler content. Slightly verbose with quoted action names and redundant 'webhook' references, but generally efficient for the dual-purpose explanation required.

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?

No output schema exists, so description must cover return values. Adequately describes list output (conditions, trigger counts, timestamps) but omits what remove returns (success confirmation, error states). Given 2-parameter simplicity, coverage is acceptable but 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 has 100% coverage establishing baseline 3. Description reinforces parameter purposes ('list to see all', 'remove with webhook_id to delete') and adds context about list output fields, which helps understand the action's utility without repeating schema definitions verbatim.

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 dual functions (list/remove) and uses specific verbs with the resource 'webhooks'. The term 'registered webhooks' implicitly distinguishes this from sibling 'set_webhook' (creation), but lacks explicit cross-reference naming the alternative tool.

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?

Provides explicit guidance on parameter values: 'Use action list to...' and 'Use action remove with...'. Clearly maps actions to outcomes. Lacks explicit 'when not to use' guidance (e.g., not for creating webhooks) though this is implied.

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