git_webhook

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

With no annotations, the description carries the full burden. It does disclose that webhook URLs are secrets and that confirm is required, which is useful behavioral context. However, it does not describe the side effects of rotation, such as whether the old webhook is invalidated, nor does it mention permissions or reversibility.

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 extremely concise: a front-loaded purpose sentence followed by a compact args list. Every line adds necessary information, and there is no filler or redundancy.

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?

For a simple three-parameter tool with an output schema, the core invocation is covered. However, because there are no annotations, more context would be valuable regarding what happens during rotation, whether the operation is destructive, and any required prerequisites. The description is adequate but not fully complete.

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 description coverage is 0%, and the description compensates by defining all three parameters: username as the owning user, uuid as the application uuid, and confirm as required due to secrets. This adds meaning beyond the schema's bare property names and types.

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 states a specific verb-resource pair: 'Create or rotate the deploy webhook for a git application.' This clearly identifies the operation and target, and distinguishes it from sibling git tools like git_get, git_deploy, and git_fetch, which involve 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?

No explicit guidance is given about when to use this tool versus alternatives. It does not mention prerequisites, when rotation is appropriate, or why a user would choose this over other git-related tools. The only implicit hint is that confirmation is required due to webhook URLs being secrets.

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