add_account

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

The description adds significant behavioral context beyond annotations: atomicity, backup/validation, and the privacy property of cookie_file. Annotations are minimal, so the description carries the burden well.

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 sentences with no filler. It front-loads the core action and then elaborates key parameters, achieving high information density per word.

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 presence of an output schema (not shown) and 6 parameters (1 required), the description covers the most important behavioral aspects (atomicity, cookie handling) but does not explicitly mention which parameter is required.

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 compensates partially by detailing cookie_file and persona. However, it omits explanations for proxy, is_active, target_keywords, leaving gaps for half the parameters.

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 verb 'Add' and the resource 'account to config/accounts.json', specifying it is validated, backed up, and atomic. It distinguishes this from sibling tools like update_account and remove_account by focusing on creation.

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 provides clear context for the cookie_file and persona parameters, including constraints (path on this machine, max 4000 chars) and behavior (cookie values never pass through). However, it does not explicitly state when to use this tool over alternatives like update_account.

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