Войти в Яндекс

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

With no annotations, the description carries the full disclosure burden. It reveals that the browser window is visible, the session is saved to the profile, and the server runs headless afterward, which is valuable behavioral context beyond trivial statements.

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 concise sentences, each adding distinct value: the action performed, the session persistence, and the usage frequency. There is no redundancy or verbosity, and the key information is front-loaded.

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 description covers purpose, side effects, and usage scenarios, which is sufficient for a tool with no parameters and no output schema. It could mention how to verify successful login (e.g., via login_status), but the essential information is present.

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 tool has zero parameters, so the schema provides complete coverage. The description appropriately describes the parameterless action and its effect, meeting the baseline for parameterless tools.

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 tool opens a visible browser window for Yandex login and persists the session, which is a specific verb+resource. It distinguishes itself from sibling tools like login_status by describing the interactive login flow.

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 explains that the tool is typically called automatically on first access and only needs to be run once per computer, giving clear context on when manual invocation is appropriate. It does not explicitly mention alternatives like login_status, but the guidance is adequate.

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