veil_set_fingerprint

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

With no annotations, the description fully discloses behavior: when injected values take effect (next navigation), which overrides are immediate, and a caveat ('not a magic bullet'). No contradictions.

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?

Four sentences pack a lot of information without redundancy. The key verb 'Apply' and resource 'COHERENT fingerprint' are front-loaded, and every sentence 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 the tool's complexity (multiple parameter types, nested object, no output schema), the description covers purpose, usage, timing, and limitations comprehensively, leaving no obvious gaps.

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?

The description adds significant meaning beyond the schema's property descriptions, explaining the purpose of each parameter (preset, random, seed, fingerprint) and emphasizing internal consistency requirements.

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 applies a coherent fingerprint/profile, listing all components (UA, client hints, screen, timezone, etc.), and distinguishes from siblings by emphasizing 'coherent identity control' and timing relative to veil_goto.

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?

Explicitly says to call before veil_goto for full effect and notes that some overrides apply immediately. Does not mention when not to use or alternative tools, but provides clear context for when to use.

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