addPrivacyNative

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

Without annotations, the description carries full burden. It mentions the action (adds native blocker) and adds the safety context, but does not disclose whether the operation is destructive, reversible, or requires specific permissions. The safety note hints at potential risk but lacks 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?

Two concise sentences: first states the core purpose with examples, second provides a critical safety warning. No fluff or redundancy, every word 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?

Given many sibling tools and no output schema, the description is adequate but could be more complete. It does not explain what 'native' means, how it differs from addPrivacyBlocklist, or what behavior to expect after addition. The safety note mitigates some missing context.

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 describes the parameters well. The description adds examples of what 'id' might be (Alexa, Roku) but does not add significant meaning beyond the schema. Baseline 3 is appropriate.

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 native tracking protection blocker to a profile, with concrete examples like Alexa, Roku, Samsung. This verb+resource combination is specific and distinguishes it from sibling tools like addPrivacyBlocklist or addToAllowlist.

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 clear usage condition: only use with designated test profiles. This helps prevent misuse but does not explicitly state when not to use or list alternative tools for similar tasks.

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