delete_egress_allowlist_entry

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

Annotations already flag destructiveHint=true and idempotentHint=false, but the description goes well beyond them: it names the blast radius (breaking integrations relying on the destination), states the operation cannot be undone by this tool, discloses the expected response (acknowledgement or HTTP 404), and notes the organisation permission requirement.

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?

Every sentence earns its place: identity, consequence, prerequisite, irreversibility, and return/auth facts, with the harm warning front-loaded rather than buried.

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 single-parameter destructive delete with an output schema, the description supplies everything the agent needs — danger framing, prerequisite lookup, irreversibility, and permission scope — and the return contract is already covered by the output schema.

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 100% and the single 'id' parameter is documented in the schema with its UUID format and a pointer to list_egress_allowlist / create_egress_allowlist_entry as sources. The description adds no further parameter meaning, so baseline 3 applies.

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?

States a specific verb (Remove) and resource (organisation egress allowlist entry) with the exact namespace and scope, so it is immediately distinguishable from update_egress_allowlist_entry or get_egress_allowlist_entry. The consequence clause reinforces what removal actually means.

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?

Explicitly instructs the agent to call get_egress_allowlist_entry first, which is a concrete prerequisite step. It does not, however, state when deletion is inappropriate versus updating the entry, nor name an alternative for reversible changes.

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