rb2b_native_webhook

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

No annotations are provided, so the description must fully disclose behavior. It mentions 'pushed into the specified audience' but doesn't explain whether this creates a new lead, updates an existing one, or requires authentication. The lack of details on potential side effects (e.g., duplicate handling) is a significant gap.

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: only two sentences that convey the purpose and core action without extraneous words. Every part is essential and earns its place, making it efficient for an AI agent to parse.

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?

Given the tool has 1 optional parameter and no output schema, the description is mostly adequate but lacks completeness for a webhook tool. It doesn't clarify what happens when audienceName is omitted (using the default), error conditions, or what triggers the push. This is a minimal viable description but leaves some ambiguity.

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 100% (the single parameter audienceName has a description: 'Audience name to push visitors into'). The description adds no extra meaning beyond the schema, but since schema coverage is high, the baseline of 3 is appropriate. The justification mentions the parameter explicitly in the description, earning a 4 for clarity.

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 is a 'Webhook endpoint for RB2B website visitor tracking' and explains the action: 'Each visitor is pushed into the specified audience.' This gives a specific verb+resource combination, distinguishing it from sibling tools like 'warmly_native_webhook' and 'vector_native_webhook' by name and purpose.

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 usage for tracking website visitors and assigning them to an audience, but lacks explicit guidance on when to use this tool versus alternatives like 'warmly_native_webhook' or 'vector_native_webhook'. No information on prerequisites, setup steps, or exclusions is provided.

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