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

Annotations already declare this is a mutation (readOnlyHint=false), open-world, non-destructive, and non-idempotent. The description adds genuinely useful context the annotations cannot convey: while disabled, ingest posts are refused, which tells the agent the effect is immediate and externally visible. It stops short of covering authorization, whether existing queued documents are retained, or how re-enabling affects missed posts.

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?

A single front-loaded sentence with zero filler and the side effect parenthesized inline. Nothing is wasted, though the terseness comes at the cost of the missing guidance noted elsewhere.

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 3-parameter mutation with two undocumented parameters and no output schema, the description should say how to obtain webhook_id, who may toggle it, and what the call returns or preserves. As written, an agent knows the intent but not enough to call it confidently the first time.

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 only 33% — only app_id is documented, while webhook_id and the enabled boolean are bare. The description's 'off ... or on again' loosely maps to the enabled flag but adds no syntax, default, or identifier guidance, so it fails to compensate for the coverage gap.

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?

States a specific verb (turn off/on) and a specific resource (ingest webhook), plus the operational consequence '(posts are refused)'. It is distinguishable from siblings like list_knowledge_webhooks, though it never names an alternative tool explicitly.

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?

There is no when-to-use guidance beyond the implicit toggle action: no mention of prerequisites (e.g., needing a webhook_id from list_knowledge_webhooks), no permission requirements, and no statement about when disabling is preferable to other remediation steps.

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