update_account

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

Discloses that the warm browser session is closed and next action cold-starts on new config. Without annotations, this side effect is critical and well communicated.

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?

Three sentences, no wasted words, front-loaded with purpose, and logically ordered.

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?

Covers the core behavior and significant side effects. While not all 9 parameters are detailed, the output schema exists to fill return value details.

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 coverage, the description explains proxy, persona, and cookie_file. However, it does not cover is_active, self_handles, action_config, target_keywords, or 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?

Clearly states 'Partially update an account' and lists specific fields that can be changed (proxy, persona, cookie_file). Distinguishes from sibling tools like add_account and remove_account.

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?

Describes how to clear fields (empty string for proxy and persona) and mentions that cookie_file re-imports like add_account. Provides implicit context for when to use, though no explicit exclusions.

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