addPrivacyBlocklist

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

No annotations are provided, so the description carries full burden. It states the operation is an addition (write), but does not disclose behavioral traits such as whether it overwrites existing blocklists, requires specific permissions, or what happens on duplicate attempts. The safety note hints at restricted use but lacks depth.

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 sentences: first clearly states the purpose, second provides a crucial safety note. Front-loaded with action, no redundant or vague wording. 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?

For a simple tool with 2 parameters and no output schema, the description is minimally adequate. It explains what it does and warns about test profiles. However, it lacks information about return values, idempotency, or interaction with other blocklist-related tools.

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 baseline is 3. The description adds no extra meaning beyond what the schema already provides (profile_id and id). No syntax, format, or behavioral constraints (e.g., valid domain formats) are mentioned.

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 adds a privacy protection blocklist to a profile. The verb 'adds' and resource 'privacy protection blocklist' are specific. However, it does not explicitly differentiate from similar sibling tools like addToDenylist, which adds to a denylist, leaving potential ambiguity.

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?

The safety note provides a condition ('only use with designated test profiles'), which guides usage. However, there is no when-not-to-use guidance, no mention of prerequisites, and no comparison to alternatives like removePrivacyBlocklist or replacePrivacyBlocklists.

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