remote_session_execute

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

The description reveals that the tool waits for completion, which is important behavioral context. Since no annotations are provided, it carries the transparency burden, but it does not mention prerequisites (e.g., session must already exist), error behavior, or how timeout/output_limit affect execution.

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, tightly worded sentence that front-loads the core action. Every word contributes to the purpose and behavioral overview, with no filler.

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 tool with four parameters and a prerequisite (persistent session), the description is too sparse. While the presence of an output schema covers return values, the description fails to address session existence, timeout behavior, or output limits, leaving significant gaps for an agent to infer.

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?

With 0% schema description coverage, the description should compensate, but it only implicitly references 'name' via 'named persistent session' and 'command' via 'Run a command'. It provides no detail about the 'timeout' or 'output_limit' parameters, leaving their semantics unexplained.

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 action: 'Run a command inside a named persistent session and wait for completion.' This is specific and distinguishes it from generic 'remote_execute' by highlighting the persistent session context.

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?

It clearly implies when to use this tool—inside a named persistent session—and indicates blocking behavior. However, it does not explicitly state when not to use it or suggest alternatives like 'remote_execute' for non-persistent commands.

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