Complete TOTP verification for metrics

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

Annotations already mark this as non-readOnly and non-idempotent, and the description confirms a state-changing action without saying what side effects occur. It does not disclose what happens to the session on failure, whether a completed verification can be reused, or any rate/retry 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 short and front-loaded, but the first sentence merely restates the tool title and adds little information. The second sentence is useful, so the overall length is acceptable.

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 multi-step authentication completion tool with no output schema, the description omits prerequisites, return values, error cases, and what happens after the connection is completed. An agent cannot reliably know how to obtain sessionId or judge success.

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?

With 0% schema description coverage, the description needed to explain both parameters but only implies the role of totpCode ('Verifies the TOTP code'). sessionId is left completely unexplained, and there is no mention of formats such as six-digit codes or where the session identifier comes from.

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 and resource: 'Verifies the TOTP code and completes the metrics SSH connection.' This distinguishes it from generic connection tools, though it does not fully explain what 'completes' means or that this is likely the second step of an existing authentication 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?

There is no guidance on when to use this versus related TOTP tools such as termix_docker_verify_totp_complete_connection or termix_files_verify_totp_complete_connection. It never mentions the need for a prior step, the role of sessionId, or prerequisites for calling this tool.

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