stalwart_unallow_ip

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

No annotations were provided, so the description carries the burden. It explicitly labels the operation 'Destructive' and warns that confirm=True is required, which discloses a key behavioral trait. It also specifies the resource being removed (an IP from the allowlist). The source for the ip_id adds prerequisite context, though it doesn't discuss reversibility or authorization.

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 three lines, front-loads the purpose and destructiveness, and then lists the two args with brief, necessary explanations. Every sentence contributes.

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 two-parameter removal tool, the description provides purpose, prerequisite lookup, and a mandatory confirmation flag. An output schema exists, so return-value documentation is not needed. It is sufficiently 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?

The schema only shows 'Ip Id' and 'Confirm' with no descriptions. The description adds crucial semantics: ip_id is an allowed IP id obtained from stalwart_list_objects(obj_type='allowed_ip'), and confirm must be True to proceed. This fully compensates for the missing schema descriptions.

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 opens with 'Remove an IP from the allowlist,' a specific verb+resource statement. This clearly identifies the operation and distinguishes it from siblings like allow_ip, block_ip, and unblock_ip.

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?

It provides clear context by requiring the allowed_ip id to be fetched from stalwart_list_objects, and explicitly notes the confirm parameter must be True. It does not explicitly contrast with alternatives like unblock_ip, but the instruction is unambiguous.

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