serial_shell_login

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

No annotations provided; description discloses the combined behavior (connect, detect PSH, auto-unlock) but does not mention error handling, return format, or whether it is destructive or safe.

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?

Two sentences, front-loaded with 'one-click serial login', no unnecessary words. Every sentence adds value.

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?

Describes the combined workflow and return of a 'ready session', but lacks details on return structure, failure modes, and prerequisites (e.g., device connectivity). Adequate but not fully comprehensive.

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 covers all three parameters with descriptions; the description adds minimal new meaning beyond restating purpose (e.g., 'unlock key/password' for key). With 100% schema coverage, baseline 3 is appropriate.

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 clearly defines the tool as 'one-click serial login' that combines open, PSH detect, and unlock into a single call, and it distinguishes from granular sibling tools like serial_open and serial_exec.

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 implies usage for simplified login but does not explicitly state when to use this tool versus alternatives (e.g., serial_open + serial_exec), nor does it outline prerequisites or exclusions.

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