mt4_control

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

No annotations provided, so description carries full burden. It discloses that mutating a live terminal requires confirm=true, highlighting a critical safety constraint. This is adequate for a tool with a defined action set.

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?

Six-line description is extremely concise. First sentence states main purpose. No 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 3 params and no annotations, description covers the essential behavioral trait (confirm for live). Output schema exists, so return values need not be described. Minor lack of detail about terminal format, but acceptable.

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 coverage is 0%, but description explains all parameters: terminal, action (listing three options), and confirm (with usage condition). Adds meaning beyond schema structure.

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 'Start, stop, or restart a terminal's systemd unit,' specifying the verb and resource. It distinguishes from siblings like mt4_deploy or mt4_autotrading, which have different purposes.

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?

Provides explicit condition for confirm parameter when mutating a live terminal. Though it doesn't directly compare to alternatives, the action set (start/stop/restart) is self-contained and clear.

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