exec

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

No annotations provided, so description must disclose behavioral traits. It states return values (stdout, stderr, exit_code) but omits details like timeout behavior, security implications, or that the command runs with the session's user permissions. The description is insufficiently informative.

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?

Single sentence with no unnecessary words. Efficiently conveys core action and return values.

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 simple execution tool with full schema coverage, the description is mostly complete. It mentions return values and implies the remote session context, though it could explain how to obtain a session_id or that the session must be active.

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 100%, so baseline 3. The description adds no extra meaning beyond the schema; it does not clarify parameter relationships, defaults, or usage patterns (e.g., how timeout affects execution).

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 identifies the tool's action: executing a shell command on a remote session. The verb 'Execute' and resource 'shell command on a remote session' are specific and distinct from sibling tools like docker_exec or file_read.

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 (e.g., docker_exec for containerized commands). The description does not specify prerequisites like needing an active session, nor does it caution against long-running or destructive commands.

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