replaceDenylist

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

Explicitly states that the operation is destructive ('removes all existing entries and replaces them'). Without annotations, this disclosure is valuable. Could have mentioned idempotency or authentication needs, but the main behavioral trait is covered.

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?

Extremely concise: two short sentences plus a warning and safety note. Key information is front-loaded, and every sentence adds value.

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 essential behavior, destructiveness, and usage suggestion. Lacks explicit mention of return type or idempotency, but given tool simplicity and good schema coverage, it is largely 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?

Schema coverage is 100%, so the description provides no additional parameter details beyond what the schema already offers. The description indirectly refers to the body parameter as 'provided list of domains' but does not elaborate on profile_id.

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 states it replaces the entire denylist with a provided list of domains, using a specific verb 'replaces' and resource 'denylist'. It distinguishes from sibling tools like addToDenylist which adds individual entries.

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?

Includes a warning about removing all existing entries and a safety note to only use with test profiles, providing context for when to use. However, it does not explicitly mention alternatives or when not to use the tool.

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