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

Annotations already indicate destructive and idempotent characteristics; the description adds specific context by stating that absent entries are ignored, which clarifies the idempotency behavior and that the operation is non-fatal. This goes beyond the hints and provides useful operational detail.

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?

Three concise sentences with no fluff. The core action is front-loaded, the behavior for absent entries is clearly stated, and the alternative for clearing the list is provided. Every sentence earns its place.

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?

The description covers purpose, key behavior, and alternative usage. It mentions the scope ('private site's allowlist') and does not rely on an output schema. It could theoretically mention error conditions or required permissions, but for a simple removal tool this is adequate and complete relative to its complexity.

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 schema already documents the allowlist parameter as 'Entries to remove'. The description reinforces this by mentioning email/domain (matching the kind enum) and adds the idempotency semantics ('entries that are not present are ignored'), which adds value beyond the schema.

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 clearly specifies the verb 'remove' and the resource 'specific email and/or domain entries from a private site's allowlist', and distinguishes it from set_allowlist by noting that it leaves everyone else on the list. This makes the purpose unambiguous and distinct from sibling tools like add_to_allowlist or set_allowlist.

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 explicitly directs when to use an alternative ('To clear the whole list, use set_allowlist with an empty array') and implies this tool is for targeted removals. It does not explicitly mention conditions like when not to use it or prerequisites, but the given guidance is sufficient for common use cases.

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