⚠️ Enable webhook

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

Description confirms the destructive nature (changes account settings, causes external events) and mentions confirmation required. No contradiction with annotations. Adds value beyond annotations by explaining security and default confirmation.

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?

Concise, front-loaded description with no redundant sentences. Each sentence adds necessary information.

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?

Covers main purpose, security, confirmation, and related tools. Without output schema, does not explain return values, which is acceptable. Fairly complete for this tool.

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 provides full parameter descriptions (100% coverage). Description adds context about URL matching and security, enhancing understanding beyond schema. Baseline 3, extra context merits 4.

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?

Description clearly states it subscribes the server's URL to webhook notifications for messenger events. It distinguishes from siblings like messenger_get_subscriptions and messenger_post_webhook_unsubscribe.

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?

Describes when to use (to subscribe for webhooks) and specifies security constraint. Mentions related tools for checking and unsubscribing. Does not explicitly state when not to use, but context is clear.

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