profile_save

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It usefully explains what is saved (cookies + localStorage), from where (live browser), and to where (specific JSON path). It does not address whether the save overwrites/merges an existing profile or what happens if the profile already exists, leaving some behavioral ambiguity.

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 compact and front-loaded: the action and purpose appear in the first clause, and the precise file path is added in the second sentence. No filler or redundant information.

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 single-parameter tool with an output schema known to exist, the description covers the essential invocation details: what is saved, why, and the storage path. It could be more complete by noting overwrite behavior, but an agent already has enough to call it correctly.

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?

There is only one parameter and the schema description coverage is 0%. The description gives 'name' concrete meaning by mapping it to the profile name and embedding it in the file path, which is valuable context beyond the bare schema. It only misses explicitly reminding the agent that the parameter has a default value, but the schema already supplies that.

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 a specific action ('Сохранить куки + localStorage'), the resource being acted on (the live browser), and the destination profile. This clearly distinguishes it from its sibling profile_load, which is the opposite direction.

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 parenthetical '(логины не терять между сессиями)' implies the use case: persist authenticated state across sessions. However, it does not explicitly state when to call this tool vs. alternatives, nor does it mention profile_load as the restoring counterpart, so an agent must infer the usage context.

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