ecp_git_webhook_delete

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

The description discloses that the operation is 'Irreversible', a key behavioral trait. However, with no annotations provided, it carries the full burden of behavioral disclosure but does not mention other aspects like required confirmation (though the schema implies it) or any side effects beyond permanence.

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, using two short sentences to convey purpose and a critical caveat. It is front-loaded with the action and resource, and every word earns its place.

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 delete operation with only two parameters and no output schema, the description is fairly complete. It states the action and irreversibility, but it could have mentioned the confirmation requirement or the impact on the app's deployment workflow. Given the simplicity, it is adequate but not rich.

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 description provides no explanation of the parameters app_id and confirm. Schema coverage is 0%, so the description should compensate but does not. The confirm parameter's const true requirement is only visible in the schema, and the description does not clarify that confirmation is mandatory.

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 verb 'Delete' and the resource 'an app's deploy webhook', making the operation unambiguous. It also distinguishes from sibling webhook tools like get, create, update, and rotate_secret by specifying the destructive action.

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?

There is no guidance on when to use this tool versus alternatives. It does not mention conditions, prerequisites, or any exclusions. The agent is left to infer that deletion is appropriate only when a webhook should be removed permanently.

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