Create profile

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

Beyond the annotations (openWorldHint=false, destructiveHint=false), the description discloses that omitted fingerprint fields are auto-generated as a coherent random fingerprint, explains proxy modes (static vs rotating), notes advanced field merging behavior, and states the return value (profile_uuid). This adds meaningful behavioral context.

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 focused sentences, front-loaded with the primary action. Every sentence provides value: defaults, proxy binding, advanced overrides, and return value. No redundancy or 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?

Given the complexity (8 parameters, nested objects, no output schema), the description covers the required parameter, defaults, proxy modes, advanced overrides, and return value. It could mention what happens if proxy is omitted entirely, but the schema already handles that. Overall, it is sufficiently complete for a create tool.

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 the baseline is 3. The description adds extra meaning by clarifying that `proxy` static refers to saved proxies from list_proxies and rotating is dynamic residential, and that `advanced` follows the FlashID Local API shape. This goes beyond the schema descriptions.

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 opens with 'Create a browser profile,' making the verb and resource explicit. This clearly distinguishes it from sibling tools like update_profile, delete_profile, and get_profile.

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 explains key usage details ('Only `system` is required', 'Bind a proxy via `proxy`', 'Fine-grained fingerprint control goes in `advanced`') but does not explicitly contrast with alternatives or state when not to use. The usage context is implied rather than explicitly differentiated from update_profile.

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