manus_webhook_delete

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

The description states the immediate behavioral consequence ('The endpoint will stop receiving notifications immediately'), adding value beyond the tool's name. Since no annotations are provided, this disclosure is important, though it could mention permanence or prerequisites.

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 extremely concise, using two short sentences that front-load the action and consequence without any unnecessary words.

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 delete tool with one required parameter and no output schema, the description adequately covers the primary effect. However, it omits details about irreversibility or return values, which would be helpful.

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?

The input schema has 0% description coverage and the description does not elaborate on the single required parameter 'webhook_id', leaving its format, origin, or constraints unstated.

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 (delete) and the resource (webhook), and it distinguishes the tool from sibling tools such as 'manus_webhook_create' and 'manus_webhook_list' by specifying the immediate effect of stopping notifications.

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 that the tool should be used when you want to stop receiving notifications from a webhook, but it provides no explicit guidance on when not to use it or what alternative tools might be suitable.

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