list_webhook_logs

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

No annotations are provided, so the description must disclose behavioral traits. It states that logs are recent and include status/response details, but it omits pagination behavior, sorting, rate limits, or what 'recent' means. This is insufficient for a tool with zero annotations.

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 a single sentence of 15 words with no wasted information. It is front-loaded with the verb and resource, making it concise and easy 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 three simple parameters and no output schema, the description is minimally adequate. It hints at return content (status, response details) but fails to explain pagination, date range, or sorting. A more complete description would cover these aspects.

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 coverage is 100%, so the parameters (id, page, limit) are fully described in the schema. The description adds no extra meaning beyond 'list recent delivery logs', which does not clarify how parameters affect the output. Baseline 3 is appropriate.

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 'List' and resource 'delivery logs for a webhook', which clearly indicates the tool's function. It effectively distinguishes from sibling tools like 'list_webhooks' (which lists webhooks themselves) and 'get_webhook'.

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 use for viewing delivery logs but does not explicitly state when to use it versus alternatives. No exclusions or conditions are provided, leaving the agent without clear guidance.

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