exec

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

No annotations are provided, so the description carries full burden. It discloses key behaviors: command execution, CWD, length limit, and failure for restricted shell access. However, it does not mention security implications, output format details, or timeout behavior, leaving some gaps.

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 compact, with two main sentences followed by targeted caveats. Every sentence adds specific, actionable information. It is well-structured and easy to scan, avoiding unnecessary verbosity.

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?

Given the presence of an output schema, the description does not need to detail return values. It covers essential execution context (CWD, length limits, failure cases) for a command execution tool. While more details on parameter interactions would help, the description is sufficiently complete for typical use.

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 only 25% (only 'command' has a detailed description). The description adds value by explaining CWD, length limits, and shell access constraints, but does not detail the 'subscription', 'stdin', or 'env' parameters. It partially compensates for the low schema coverage but not fully.

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 that the tool executes a command on the Plesk server and returns the result, providing a specific verb and resource. However, it does not explicitly differentiate from sibling tools like api_call or upload, though the distinct function is obvious from 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?

The description provides practical usage constraints such as CWD behavior (e.g., '/root' for root user), a character limit of ~740 characters, and failure conditions (no or chrooted shell access). It does not explicitly state when to use this tool versus alternatives, but the constraints themselves guide appropriate use.

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