mngt_sshtimeout

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

No annotations are provided, so the description carries the behavioral disclosure burden. It does explicitly state that this is a write operation and that confirmation is required, which are useful signals. However, it does not explain the confirmation workflow, side effects, persistence, or impact on existing SSH sessions.

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?

One compact sentence with no filler. Each phrase adds value: the operation, the target resource, the write nature, and the confirmation requirement.

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 write tool that requires confirmation, the agent has no way to know how to obtain confirmation_id or confirm_token, or what response to expect. With no annotations and no output schema, the definition is too sparse for reliable invocation.

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 0%, and the description adds no parameter-level meaning. The 'minutes' parameter is inferable from the tool name, but user_code, confirm_token, and confirmation_id are not mapped to the confirmation process described.

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 uses a specific verb-resource pair, 'Set SSH session timeout', which makes the operation unambiguous. It implies differentiation from sibling tools like mngt_sshport and mngt_telnettimeout, but does not explicitly name them.

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 tool versus similar management settings such as mngt_telnettimeout or mngt_sshport. The only usage hint is that confirmation is required, with no elaboration on prerequisites or exclusions.

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