manus_webhook_events_clear

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

The description mentions deletion from the 'local store' but does not disclose whether the operation is irreversible, what authentication is required, or if it affects other resources. Without annotations, this is a significant gap for a mutation tool.

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?

Two sentences, front-loaded with the primary action and object, followed by a concise usage guideline. No 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?

The description covers the core purpose and filter logic, but lacks details on return value, permanence, and relation to other webhook tools. For a simple delete operation, it is adequate but not fully comprehensive.

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 only 33% (only 'before_received_at' has a description). The description adds that filters can be used in any combination, but does not explain the meaning of 'event_type' or 'task_id' beyond schema names. It partially compensates by stating the 'no filters' behavior.

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 it deletes webhook events from the local store, with a specific verb 'delete' and a resource 'webhook events'. While it does not explicitly distinguish from sibling tools, the action is distinct from other webhook event tools like 'get' or 'list'.

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 provides guidance on filtering: 'Provide any combination of filters; no filters = delete everything.' However, it lacks explicit guidance on when to use this tool versus alternatives, such as when to delete locally vs. on the server.

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