run_webhook

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

No annotations are provided, so the description bears full responsibility. It discloses key behaviors: the URL structure, the test mode requirement, and queue mode response handling. It does not cover rate limits or authentication, but the disclosed traits are essential for correct use.

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 concise, front-loading the purpose and following with key details in a single paragraph. It could be slightly more structured, but every sentence contributes meaningful information without fluff.

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 tool has no output schema, yet the description does not explain what the call returns (e.g., response body, status codes). It does cover essential behavior like test mode and queue mode, but lacks completeness regarding output and error handling. Given the complexity of a webhook trigger, more detail would be beneficial.

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%, and the description adds contextual value beyond the schema by explaining the URL pattern and the test mode condition. This helps the agent understand the relationship between parameters and behavior, elevating it above the baseline of 3.

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 tool triggers a workflow via its Webhook node, identifying the specific action and resource. It distinguishes from sibling tools like activate_workflow or deactivate_workflow by focusing on webhook-based triggering.

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 explains when to use the tool and provides important context such as the test URL mode requiring the workflow open in 'Listen for test event' mode, and the queue mode behavior. It does not explicitly mention when not to use it, but the context is sufficient for an AI agent.

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