execute

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It effectively describes key behaviors: it's a remote execution tool (implies mutation/action), mentions dangerous command detection (safety mechanism), timeout defaults, and working directory defaults. However, it doesn't specify authentication requirements or rate limits, which would be helpful for a tool with potential security implications.

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 perfectly structured and concise: a clear opening sentence states the purpose, followed by well-organized parameter explanations in bullet-like format, and ends with return value information. Every sentence adds value with no redundancy or wasted words.

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 tool's complexity (remote command execution with safety mechanisms), 0% schema description coverage, no annotations, but with an output schema present, the description provides excellent completeness. It covers purpose, all parameters with semantics, usage guidance, safety warnings, and references the return format (though the output schema handles details). No significant gaps remain for agent understanding.

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 fully compensates by providing detailed semantic information for all 5 parameters. Each parameter gets clear explanations: 'server' includes format examples and references 'list_servers', 'command' defines its purpose, 'timeout' specifies units and default, 'working_dir' explains default behavior, and 'force' includes a strong caution about bypassing safety checks.

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 purpose with a specific verb ('execute') and resource ('shell command on a single SSH server'), distinguishing it from siblings like 'execute_on_group' (which handles multiple servers) and 'list_servers' (which only lists servers). It explicitly defines the scope as a single server operation.

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 guidance on when to use this tool vs alternatives: it mentions 'Use list_servers to see available servers' for prerequisite information and implicitly distinguishes from 'execute_on_group' by specifying 'single SSH server' (vs group execution). It also warns about the 'force' parameter for dangerous commands.

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