get_webhook_logs

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

With no annotations, the description alone must disclose behavioral traits. It explains date format (ISO-8601) and status filter values, but omits details on sorting (sort_by_newest parameter not mentioned), pagination behavior, potential rate limits, or auth requirements. The lack of annotation support makes the description insufficient.

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 sentences, front-loaded with the main action and structure, followed by concise parameter details. No extraneous information.

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 8 parameters, no output schema, and no annotations, the description is incomplete. It covers basic purpose and a few parameters but misses workspace_id, sort_by_newest, and any details on response structure or required webhook_id. Significant gaps remain.

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 0%, so the description must compensate. It explains from_/to as ISO-8601, status as ALL/SUCCEEDED/FAILED, and mentions page/size are query params. However, it does not describe workspace_id, sort_by_newest, or provide exact syntax for date parameters. Adds value but incomplete.

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 clearly states 'Get a webhook's delivery logs', which is a specific verb+resource combination. It differentiates from sibling tools like 'get_webhook' (gets a single webhook configuration) and 'list_webhooks' (lists all webhooks) by focusing on logs.

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?

No guidance on when to use this tool versus alternatives. The description mentions 'POST filter body' and 'page/size are query params', but does not provide context on when it is appropriate to call this vs. other webhook-related tools.

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