webhook_deliveries_create_instance

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

No annotations are provided, so the description carries the full behavioral burden and delivers almost none of it. It does not state that this is a write/mutation, whether auth or a specific role is required, whether the operation is idempotent, or what a successful creation returns. Pointing at 'components.schemas.WebhookDeliveryCreateRequest' is a pointer, not behavioral disclosure.

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 text is short but not efficient: 'POST /v1/webhookDeliveries (POST /v1/webhookDeliveries)' duplicates the identical path in parentheses, which is pure waste. The one substantive clause merely defers to an external spec, so the brief length reflects under-specification rather than tight writing.

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 mutation tool with no annotations and no output schema, this description is grossly incomplete. It provides no information about effects, permissions, or results, and it offloads everything to an OpenAPI document the calling agent may not even have access to.

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%, so the single 'body' parameter is already documented by the schema. The description's reference to the same schema adds no syntax or field-level meaning beyond what the structured data provides, which lands at 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 only restates the HTTP verb and path ('POST /v1/webhookDeliveries'), which is essentially a tautology of the tool name. It never explains what a webhook delivery is or what creating one accomplishes, and it does nothing to distinguish this from siblings like webhook_pings_create_instance or webhooks_create_instance.

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 when-to-use guidance, no prerequisites, and no reference to alternatives. The agent is left to infer from the name alone that this creates a webhook delivery record, with no context on when that is appropriate.

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