remove_approval_gate

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

With no annotations, the description must carry the safety profile, and it does disclose the key effect: merges become unprotected. However it omits whether removal is reversible, what permissions beyond tier are needed, and whether existing sign-off records are destroyed. The upsell paragraph adds words without adding behavior.

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 behavioral content is correctly front-loaded in the first two sentences, but the tier requirement is stated twice ('Business+ tier' and 'Requires Kiln Business') and a marketing paragraph plus upgrade URL pad the definition without aiding invocation.

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?

This is a mutation tool with no annotations, no output schema, and undocumented parameters. The description conveys the effect but not the prerequisites of state, the legal artifact types, or the failure modes an agent needs before calling it.

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 coverage is 0% for all three required parameters. The description only obliquely gestures at branch_name via 'the target branch' and says nothing about artifact_type (what values are legal) or artifact_id, so most of the parameter surface remains unexplained.

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 first sentence names a specific verb and resource ('Remove an approval gate') and the second states the concrete consequence: merges on the target branch return to unprotected. That distinguishes it from set_approval_gate and list_approval_gates, though the description never names those siblings explicitly.

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?

A prerequisite is given ('Requires Kiln Business'), which is genuinely actionable, but there is no guidance on when to remove a gate versus listing or re-setting one, and no note on whether the gate must exist first or on what happens to in-flight merges.

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