Update Account Cookies

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

The description adds context that this updates stored cookies for an existing identity and is useful for session refresh. Annotations (destructiveHint, openWorldHint) already flag a potentially destructive write, but the description does not elaborate on side effects like overwriting old cookies. Some added value, but limited.

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, front-loaded with the core action ('Update cookies...') and a practical use case. No filler or redundancy.

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?

For a simple two-parameter update tool with an output schema present, the description covers the purpose and common scenario. It does not address error handling or invalid cookie scenarios, but given low complexity and schema/annotation support, it is reasonably complete.

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 schema already documents both parameters with descriptions (account_id and cookies as a dict with c_user + xs), giving 100% coverage. The description adds no further parameter-specific details beyond the general use case, so the schema carries the semantic weight.

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 states the specific action: 'Update cookies for an existing stored Facebook identity.' This clearly distinguishes it from sibling tools like add_account or remove_account by focusing on the cookie update operation.

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?

It provides a clear use case: 'refreshing an expired session without re-adding the account.' This implies an alternative action (re-adding) and suggests when to use, but does not explicitly state exclusions or when not to use.

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