get_webhook_deliveries

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

No annotations are provided, so the description carries full responsibility for behavioral disclosure. It only says 'Fetch', without revealing pagination behavior, ordering, authentication requirements, or what 'logs' contain. Essentially no behavioral transparency beyond the action itself.

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?

A single efficient sentence that wastes no words and places the core action and scope upfront. However, it is so brief that it misses opportunities for useful detail.

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?

No output schema, no annotations, and limited description. The tool involves pagination and delivery logs, but the description does not explain return structure, ordering, or any edge cases. An agent would need to infer behavior from parameter names alone.

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 each parameter (limit, offset, invoice_id) is already documented. The description adds no extra semantic nuance, but the baseline of 3 applies because the schema carries the load.

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?

States a specific verb 'Fetch' with a specific resource 'webhook delivery attempt logs' and a clear scope 'for a specific invoice'. Unambiguously distinguishes from siblings like get_webhook_secret or get_invoice_details.

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?

Implies usage for retrieving delivery logs for an invoice, but does not explicitly state when to use it versus alternatives or provide any exclusions. No direct sibling competes, but guidance is minimal.

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