replacePrivacyNatives

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

With no annotations, the description carries the full burden. It discloses the destructive nature ('removes all existing entries') and a safety constraint ('Only use with designated test profiles'). This goes beyond the input schema. However, it does not mention return behavior or authentication needs.

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?

The description is concise, consisting of two sentences plus a warning and safety note. It is front-loaded with the main action and uses formatting (bold) for emphasis. No extraneous information.

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?

While the description covers the destructive action and safety, it is silent on the return value or response behavior. Given there is no output schema, the description should hint at what the tool returns (e.g., success confirmation or nothing). This omission makes it slightly incomplete.

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. The description does not add extra meaning to the parameters; they are already well-documented in the schema with descriptions and an example for body.

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 uses a specific verb 'Replaces' and resource 'native tracking protection collection', clearly indicating it replaces the entire collection. This distinguishes it from siblings like addPrivacyNative and removePrivacyNative which modify 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?

The description provides a warning and safety note, explicitly stating that it removes all existing entries and should only be used with test profiles. This gives clear context on when to use, though it does not explicitly name alternative tools for partial updates.

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