remote_session_password

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

With no annotations, the description carries the full burden. It discloses a critical behavioral trait: 'Input is automatically hidden in responses.' This addresses the key security concern for a password-sending tool. It doesn't cover other behaviors like error handling, but the hidden-input trait is the most important.

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 concise sentences with no wasted words. The primary action is front-loaded, and the usage guidance follows immediately. Every part contributes meaning.

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?

Considering the tool's simplicity (3 params, no output schema), the description provides the essential purpose and usage context. Combined with the fully documented schema, it gives an agent everything needed to invoke this tool correctly. The hidden-input behavior is a valuable addition.

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 schema provides 100% coverage with clear descriptions for all three parameters (password, waitTime, sessionId). The description adds no additional semantic value beyond what the schema already documents, so the baseline of 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?

The description clearly states the action: 'Send a password to a session.' It specifies the resource (session) and the purpose (password), and distinguishes itself from sibling tools like remote_session_input by emphasizing the hidden input aspect for secret data.

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 provides explicit when-to-use guidance: 'Use when prompted for sudo password, SSH passphrase, or other secret input.' It does not name alternatives or exclusions, but the context is clear and sufficient for an agent to select it for secret input scenarios.

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