Подключиться к панели

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

Adds useful behavior beyond annotations: the token is shown only once, is entered by a human, and does not appear in the conversation. This gives the agent important interaction context and complements the openWorldHint and readOnlyHint annotations without contradicting them.

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?

Four focused sentences, no filler. The primary action is front-loaded, and the credential-handling guidance and trigger condition are presented efficiently.

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 login tool, the description fully covers when to call it, what the agent should expect (window, human-entered token), and how credentials are handled. The absence of an output schema is not a serious gap here, and the parameter schema covers the remaining details.

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?

Schema coverage is 100%, so the schema already documents url and switch_account. The description adds context about the token and window flow but does not substantially deepen understanding of the two parameters beyond what the schema provides.

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?

Description states a specific action: opens a window for entering panel address and access token. This clearly distinguishes it from sibling data-management tools and from logout, even without naming alternatives.

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?

Explicitly tells when to invoke: when other tools report access is not configured or the token is no longer valid. It also explains that the human must enter the token, providing clear context for agent behavior, though it does not explicitly name alternatives or when-not-to-use conditions.

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