remove_address_list_entry

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

Discloses the destructive nature through the word 'remove' and the required write permission. Without annotations, the description adequately conveys the operation's effect, though it could detail failure modes or side effects.

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?

Two short sentences plus a clear parameter description. No wasted words; front-loads the action and requirements.

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?

Covers the core operation and parameter source. Lacks mention of return value or success/failure behavior, but for a simple deletion tool, it is largely adequate.

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?

Despite 0% schema description coverage, the description fully explains the single parameter entry_id: it is the '.id' value from address_lists, and how to obtain it.

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?

Clearly states 'Remove firewall address-list entry by id', specifying verb and resource. Distinguishes from sibling tools like address_lists (listing) and add_address_list_entry (adding).

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 lists required environment variable (MIKROCLAW_ALLOW_WRITE=true) and advises fetching the ID from address_lists first. Lacks explicit when-not-to-use or alternatives, but the context is clear for a removal tool.

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