get_webhook_info

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

No annotations are available. The description does not disclose behavioral traits such as read-only nature, potential side effects, or required permissions. It only states what the tool returns, not how it behaves.

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 that is concise and front-loaded. It contains no redundant information and is well-structured.

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?

The description is insufficient for a tool with no output schema. It mentions vague categories (settings, expiry, stats) but does not explain the structure or format of the returned data. Given the complexity of a webhook info object, more detail is needed.

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?

The sole parameter 'webhook_token' is fully described in the input schema (UUID from webhook.site). The description adds no additional meaning or context about the parameter, so it meets 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 clearly states the tool gets 'detailed information about a webhook' including settings, expiry, and stats. It distinguishes from sibling tools that focus on specific aspects (e.g., get_webhook_requests, get_webhook_url). However, it could be more explicit about what 'detailed information' encompasses.

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 is provided on when to use this tool versus alternatives like get_webhook_requests or get_webhook_url. The description does not mention any context or conditions for selection.

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