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

Annotations already declare destructiveHint=true, so the safety profile is covered. The description adds value by flagging 'WRITE' and naming the reversal tool, which the annotations do not provide. It stops short of describing idempotency or side effects, but goes beyond the structured data.

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 compact sentences with the operation type front-loaded ('WRITE.') and zero wasted words. The endpoint path is terse supporting detail.

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 two-parameter mutation tool with full schema coverage and a destructiveHint annotation, the description covers purpose, operation type, and reversal path. Only minor behavioral detail (e.g. idempotency) is missing, and no output schema is needed.

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 description coverage is 100%, so both parameters (ip and pull_zone_id) are fully documented in the schema. The description adds no parameter details beyond what the schema already provides, so the 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 and resource ('Block an IP address from a pull zone') and explicitly names the sibling inverse (bunny_remove_blocked_ip). An agent can distinguish it from bunny_remove_blocked_ip and the read siblings without opening the schema.

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?

Clearly signals the operation is a write and points to the undo tool, which gives strong context for when this tool is the right choice. It lacks explicit when-not conditions beyond that, but the reversal pointer covers the main decision need.

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