send_to_webhook

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

No annotations are present, so the description carries the full burden of behavioral disclosure. It reveals that the tool sends and gets a response, but does not disclose external network dependency, credentials or configuration needs, potential side effects on the n8n workflow, or failure behavior.

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 appropriately short and front-loaded, with the core operation in the first sentence. The Args section is mostly redundant with the schema but keeps a clear, scannable format without adding unnecessary noise.

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 single-parameter tool with an output schema, this is a minimum-viable description: it states what the tool does and what input it needs. It remains incomplete because it omits the webhook payload contract, prerequisites, and error behavior, but the low complexity and output schema reduce the burden.

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 0%, so the description must compensate. 'prompt: The text prompt to process' restates the field name and type rather than adding new meaning, and it does not explain how the prompt is used in the webhook request. This is only minimal compensation.

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 operation with a specific verb and resource: 'Send a prompt to the n8n webhook' and says it returns a response. It does not explicitly differentiate from sibling arithmetic tools, but the target and action are obviously disjoint from them.

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 guidance about when to use this tool versus alternatives, no trigger conditions, and no exclusions. 'Send to n8n webhook' implies a use case, but the description never explicitly tells the agent when this is the right choice.

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