replacePrivacyBlocklists

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

Discloses destructive behavior (removes all existing entries) and safety note, but with no annotations provided, additional details like side effects or permissions would improve transparency.

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?

Concise two sentences plus bold warnings, front-loaded with main purpose. No superfluous content.

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 key destructive replacement behavior but could mention profile existence requirement or response format. No output schema, but description is adequate for a simple parameter set.

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 description adds minimal extra meaning beyond 'provided list'. Baseline 3 applies as schema already documents parameters well.

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 the tool replaces the entire privacy blocklists collection, using a specific verb and resource. It distinguishes from siblings like addPrivacyBlocklist and removePrivacyBlocklist.

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?

Provides explicit warnings about destructive replacement and restriction to test profiles, offering clear context for use. However, lacks explicit comparison to alternatives or when-not-to-use guidance.

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