profile_load

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It states the action but does not mention that loading profile data commonly overwrites the browser's current cookies/localStorage, nor any prerequisites, side effects, or failure behavior.

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 a single compact sentence with no filler. It presents the resource and target immediately, which is appropriate for such a simple tool.

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?

The tool is simple and has an output schema, but the description leaves out important behavioral context such as whether this is a state-changing operation, whether existing browser data is replaced, and how a profile is created/loaded. The pairing with profile_save is implied but not explained.

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 description gives the single 'name' parameter meaning: it identifies the profile whose data will be loaded. This compensates somewhat for the 0% schema description coverage, but it does not explain where profiles come from, how the default value behaves, or what happens if the named profile does not exist.

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 names a specific action ('Загрузить'), a specific resource ('куки + localStorage профиля'), and a target context ('в живой браузер'). This clearly differentiates it from profile_save and other session tools in the sibling list.

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 phrase 'в живой браузер' gives clear context: this tool applies saved profile state to an active browser session. It does not explicitly mention when not to use it, but the intended usage is reasonably evident from the action described.

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