github_orgs_delete_webhook

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

No annotations are provided, and the description does not disclose behavioral traits beyond the implied destruction. There is no mention of side effects, consequences for ongoing deliveries, or permission requirements. The minimal description leaves the agent without critical safety context.

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, short sentence that front-loads the action. It is concise and efficient, but could include more detail without becoming verbose. It earns its place but leaves room for improvement.

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's low complexity (two required parameters, no nested objects, no output schema), the description is adequate but minimal. It does not mention return values or confirm deletion success. A slightly more complete description would note the HTTP response or irreversibility.

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?

Input schema coverage is 100% (both parameters described), so baseline is 3. The description does not add any additional meaning to the parameters beyond the schema definitions ('org' and 'hook_id').

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 'Delete an organization webhook' clearly states the verb (delete) and resource (organization webhook). It distinguishes itself from sibling tools like github_orgs_create_webhook, github_orgs_get_webhook, github_orgs_update_webhook, etc., which have different actions.

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. It does not mention prerequisites, irreversibility, or scenarios where deletion is appropriate. Among siblings with similar webhook operations, no comparative advice is given.

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