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

The annotations already mark this as read-only, idempotent, and non-destructive, so the safety burden is covered. The description adds useful behavioral context beyond the annotations: newest-first ordering, one entry per submission showing the latest outcome, HTTP status, error text, and pagination semantics.

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?

Two dense sentences carry all essential information with no filler. The primary output semantics are front-loaded, and the filtering/pagination details are compactly appended.

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?

With no output schema, the description adequately explains the return content: one entry per submission, latest outcome, HTTP status, and error text. Given the annotations cover safety and the schema covers required IDs, nothing essential is missing for an agent to call this tool correctly.

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 only 60%, and the description compensates well for the undocumented parameters: it explains the default and range of limit, defines before as the previous page's last occurred_at, and enumerates the status filter values. Form and webhook IDs are already documented in 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 states a specific verb and resource: it lists the delivery log of a single webhook, newest first. It clearly distinguishes this from sibling tools like get_submission_deliveries or list_webhooks by scoping to 'one webhook' and describing the entry-level content.

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 usage context is implied: use this when you need a webhook's delivery log, filterable by status, with pagination. However, the description never explicitly contrasts it with alternatives such as get_submission_deliveries or list_submissions, so the when-not-to-use guidance is missing.

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