serial_shell_login

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

With no annotations, the description carries the full burden, and it does a good job: it discloses the sequence of operations (connect, detect, unlock, return). It does not hide that it mutates state (auto-unlock) or that it establishes a session. However, it could add more context about what 'ready session' means, whether it leaves a persistent open connection, or failure 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 extremely concise and front-loaded: the first sentence states the purpose and outcome, the second explains the composite nature. Every word earns its place; no fluff or repetition.

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 composite login tool with no output schema, the description provides enough context: it tells the user what happens (connect, detect, unlock) and what to expect (ready session). It could be more complete by noting that the resulting session can be used with other serial tools, but that is implicitly understood from sibling names. Overall, it is well-suited for the tool's complexity.

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 input schema already has 100% coverage with clear descriptions for key, device, and timeout. The description does not add any extra semantic meaning beyond the schema. The baseline of 3 applies because the schema does the heavy lifting and the description does not need to compensate.

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 what the tool does: connects to a device, detects PSH state, auto-unlocks if locked, and returns a ready session. It explicitly says it combines open + PSH detect + unlock, distinguishing it from sibling tools like serial_open or serial_exec. The verb+resource model is specific and informative.

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 conveys the clear context for use: when you want a one-click login that handles connection, PSH detection, and unlocking in a single call. It implies this is a convenience wrapper over separate steps but does not explicitly name alternative tools or state when NOT to use it. That would require explicit exclusions for a 5.

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