replacePrivacyNatives

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

No annotations provided, so description carries full burden. Reveals destructive nature ('removes all existing entries and replaces them') and restricts to test profiles. Lacks details on response format or error handling, but covers key mutation behavior.

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 sentences with no waste: first states purpose, second warns of replacement, third restricts usage. Front-loaded and efficient.

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?

Description covers operation, destructive warning, and usage restriction. Does not explain response (no output schema) or error conditions, but pattern is consistent with sibling tools. Adequate for a replace operation.

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 description coverage is 100%, so baseline is 3. Description does not add any parameter-specific context beyond what the schema already provides.

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?

Description clearly states it replaces the entire native tracking protection collection with a provided list, using specific verb 'replaces' and resource 'native tracking protection collection'. Distinguished from siblings like addPrivacyNative (adds one) and getPrivacyNatives (reads).

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 safety note restricting to designated test profiles, implying caution but not specifying when to use alternatives like addPrivacyNative or removePrivacyNative. No explicit when-not-to-use or alternative tool mentions.

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