create_test_lead_submission

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

With no annotations provided, the description carries the full burden. It discloses that the delivery is synthetic, signed, queued, and intended for testing. However, it does not explain what happens after queueing, whether the delivery is observable, what errors may occur, or whether it requires an existing lead sync subscription.

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 two concise sentences. The first states the action and target, the second conveys the requirement and use case. There is no filler or redundant elaboration.

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 purpose, the test nature, and the idempotency requirement, but because there is no output schema and no annotations, the agent is left unsure about the response format, queuing semantics, and any preconditions beyond the required parameters. This is adequate but not fully complete for a tool without structured safety/output metadata.

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 75%, so the schema already documents most parameters. The description only restates that Idempotency-Key is required, which is already in the schema. It adds no meaningful semantic detail about field_values or ad_account_id beyond what the schema provides.

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 uses a specific verb ('Queue') with a specific resource ('synthetic signed lead-sync webhook test delivery') and target ('Lead Form'). It clearly distinguishes this from actual lead sync subscription tools like create_lead_sync_subscription by emphasizing it is synthetic and a test.

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 states when this is useful: 'validate webhook handling before going live.' It also notes the required Idempotency-Key, signaling correct invocation. It does not explicitly name alternatives or exclusion criteria, but the 'test delivery' framing implies it is not for production webhook traffic.

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