push_to_n8n

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

With no annotations provided, the description must fully disclose behavioral traits. It mentions the tool runs a cost audit and pushes to a webhook, and includes setup instructions. However, it lacks details on side effects, error handling, idempotency, or required permissions, leaving significant gaps.

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 well-structured: purpose first, then downstream actions, setup, event_type options, and usage examples. It is reasonably concise, though the list of downstream actions could be shortened without losing clarity.

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 basic usage and setup but omits important details: the meaning of event types, the purpose of the 'regions' parameter, and the format or content of the output (despite an output schema existing). These gaps make it only partially complete.

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. It lists event_type options ('audit_complete, anomaly_summary') but does not explain them or the 'regions' parameter at all. This adds minimal value beyond the schema.

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's purpose: 'Runs the cost audit and pushes results to your n8n workflow via webhook.' It uses specific verbs and resources, and the 'Use when' section provides concrete examples that help distinguish it from sibling tools like 'run_full_cost_audit'.

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 includes an explicit 'Use when' section with four example phrasings, giving clear context for when to invoke the tool. However, it does not explicitly mention when not to use it or suggest alternatives, which would further improve guidance.

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