github_repos_get_webhook_delivery

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

No annotations are provided, and the description fails to disclose any behavioral traits such as read-only nature, authentication requirements, rate limits, or error conditions. The description simply states the action without elaborating on side effects or limitations.

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 very concise at six words, but it lacks structural elements like bullet points or sections. While it efficiently communicates the core purpose, it could be more front-loaded with key details. The brevity is a strength but comes at the cost of completeness.

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 lack of annotations and output schema, the description is incomplete. It does not explain what a webhook delivery is, what the response contains, or how to obtain required identifiers. The agent would need prior knowledge of GitHub webhooks to use this tool effectively.

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 input schema descriptions are trivial (just parameter names like 'owner'), offering no additional meaning. The tool description does not provide any parameter context (e.g., format, constraints, or how to obtain values like hook_id or delivery_id). With schema description coverage effectively 0% meaningful, the description adds no value.

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 'Get a delivery for a repository webhook' clearly states the verb (Get) and resource (delivery for a repository webhook), distinguishing it from siblings like github_repos_list_webhook_deliveries and github_repos_get_webhook. However, it does not explicitly contrast with list_webhook_deliveries, so it is clear but not exceptional.

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 provides no guidance on when to use this tool versus alternatives, prerequisites, or scenarios where it should not be used. Sibling tools like github_repos_list_webhook_deliveries are not mentioned, leaving the agent to infer context from the name alone.

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