update_account

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

The description adds significant value beyond annotations: it explains that only provided fields change (idempotent behavior), how to clear specific fields, and that the warm browser session is closed (side effect). This aligns with annotations (idempotentHint true, destructiveHint false) and provides concrete 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?

The description is concise at 4 sentences, front-loading the purpose. Each sentence adds value, though it could be more structured (e.g., grouping parameter behaviors).

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 has 9 parameters and 1 required, the description covers key behaviors but fails to document several parameters. The output schema likely exists, but the description should at least mention the scope of partial updates. Adequate for a complex tool but with clear 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?

With 0% schema description coverage, the description partially compensates by explaining proxy, persona, and cookie_file semantics. However, it does not describe other parameters (is_active, self_handles, action_config, target_keywords, competitor_profiles), leaving gaps.

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 explicitly states 'Partially update an account' and lists the updatable fields (proxy, persona, cookie_file, etc.). It clearly distinguishes from sibling tools like add_account, remove_account, and set_account_active by focusing on partial updates.

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 implies usage for updating account settings but does not explicitly state when to use this tool versus alternatives like add_account or set_account_active. No exclusions or when-not-to-use guidance is provided.

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