send_password

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

With no annotations provided, the description carries the full burden. It thoroughly explains behavioral traits: forces terminal echo off, disables transcript logging, returns PTY bytes with password redaction, waits for quiescence or deadline expiry. No contradictions or omissions.

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 well-organized with sections, but the security model block is somewhat lengthy. However, every sentence adds value, and the structure aids readability for an AI agent.

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?

Despite no output schema, the description fully explains return behavior (redacted PTY bytes with prefix). It covers preconditions, constraints (deadline_s maximum 300s), and detailed security measures. No gaps remain for an AI agent to invoke this tool correctly.

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 33% (only deadline_s described). The description adds meaning: explains password and session_id by context, details deadline_s constraints and behavior, and the overall purpose of each parameter. This compensates for the schema gaps.

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 the tool's purpose: 'Send a password plus newline.' It further elaborates on the specific security-focused behavior (echo off, log off), distinctly differentiating it from siblings like send_text and send_line which lack these security measures.

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 specifies the prerequisite: 'Requires an existing session created via create_session(session_id, cwd).' It also implies usage context (password entry) and constrains deadline_s. However, it does not explicitly state when not to use or provide alternatives, though the security model strongly suggests it's for sensitive input only.

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