ssh_tail

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

The description does not disclose critical behavioral traits such as the streaming nature, duration (long-running), or any permissions needed. With no annotations, the agent gets no safety or behavioral context.

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 a single concise sentence with no wasted words, though it could benefit from a bit more structure (e.g., listing purpose and options).

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?

The description is very minimal for a tool with 5 parameters and no output schema. It lacks information about return format, behavior (e.g., real-time vs snapshot), and streaming considerations.

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?

Since schema coverage is 100% (all parameters explained in the schema), the description adds no additional parameter details. Baseline score 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 'tail', the resource 'remote log files', and the real-time aspect, which distinguishes it from other SSH tools like ssh_download or ssh_execute.

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?

No guidance on when to use this tool versus alternatives. For example, it doesn't mention that this is for real-time monitoring, not for static file retrieval or command execution.

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