addPrivacyNative

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

No annotations are provided, so the description carries full burden. It indicates a mutation (adding a blocker) and includes a safety note, but does not disclose potential side effects, permission requirements, or return behavior. More detail is needed for mutation tools without annotations.

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 two concise sentences, front-loading the primary action and adding a necessary safety note. Every sentence earns its place with no fluff.

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 add operation with two parameters, the description is minimally complete but lacks return value or error context. With no output schema, more detail on expected results or failure modes would improve completeness given the number of sibling 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 does not add any extra meaning beyond the schema's parameter descriptions (profile_id and id). It could clarify the format of the 'id' parameter (e.g., domain name pattern).

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 adds a native tracking protection blocker to a profile, with specific examples (Alexa, Roku, Samsung). This distinguishes it from sibling tools like addPrivacyBlocklist or removePrivacyNative.

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 restricts usage to designated test profiles, but there is no explicit guidance on when to use this tool versus alternatives like addPrivacyBlocklist. The usage context is implied but not fully clarified.

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