Submit the Telegram 2FA password

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

Annotations already declare readOnlyHint=false, destructiveHint=false, and openWorldHint=true. The description adds meaningful context that the password is used once and never stored, which is important for handling sensitive credentials, though it does not discuss failure handling for an incorrect password.

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 three short sentences: it front-loads the purpose, states the prerequisite, and adds only one important security fact. There is no redundant or filler text.

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?

Given the single required parameter, complete schema coverage, and existing annotations, the description provides enough context for safe invocation. It could optionally mention what happens after an incorrect password, but that is not essential for this narrowly scoped login step.

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 description coverage is 100%, so the password parameter is already documented in the input schema. The description adds security context about the password's lifecycle but no additional format, validation, or semantic detail beyond the schema.

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 (complete login) and resource (Telegram two-step verification password), and distinguishes this tool from telegram_login_code by requiring its passwordRequired:true result. An agent can identify its role in the login flow without opening sibling schemas.

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 explicitly says to call only after telegram_login_code returned passwordRequired:true, giving a clear prerequisite and preventing premature invocation. This is a precise condition that routes the agent correctly within the login-flow siblings.

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