cm_deactivate_webhook

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

The description adds the behavioral context that this tool 'disables' a webhook, which is not evident from the schema or annotations. The idempotentHint annotation is consistent, and no contradictions. However, it does not elaborate on reversibility or authorization requirements.

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 sentence of 7 words that front-loads the verb and resource. No redundant or irrelevant information. Every word earns its place.

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 tool with only two parameters and an idempotent annotation, the description sufficiently conveys the operation. The absence of output schema and lack of detail on return values are acceptable given the tool's simplicity. The sibling tools provide context for lifecycle management.

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% with both parameters described ('List ID.', 'Webhook ID.'). The description adds no additional meaning beyond the schema, so baseline score of 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 clearly states the action 'Deactivate (disable)' on the resource 'webhook' scoped to 'a list'. This distinguishes it from siblings like cm_activate_webhook (opposite) and cm_delete_webhook (permanent removal).

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?

The description implies usage (to disable a webhook) but does not explicitly state when to use it versus alternatives (e.g., cm_delete_webhook), nor does it provide when-not-to-use guidance. The sibling context helps, but the description itself lacks explicit guidelines.

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