Start container

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

Annotations indicate readOnlyHint=false (mutation) and destructiveHint=false, which the description aligns with. However, the description adds no behavioral detail beyond the basic action—no side effects, error conditions, or state changes. With minimal annotation coverage, the description carries little extra weight.

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 extremely terse but not efficiently so—'Start container. Starts a specific container.' is redundant and adds no new information. It under-specifies rather than being concise in a useful way.

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 two required parameters and no output schema, the description leaves out essential context: what sessionId refers to (e.g., an SSH session), prerequisites (e.g., container existence, session validity), and expected behavior on failure. The description is insufficient for reliable invocation.

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 0%, and the description does not explain what sessionId or containerId represent or how they relate to the operation. The phrase 'specific container' hints at containerId but gives no semantics for sessionId. This is a significant gap.

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?

States a clear verb and resource ('Start container') that differentiates from sibling tools like stop, restart, and pause by the action name. However, it doesn't clarify what 'starting' entails or how the container is specified beyond the parameters, so it's slightly vague but still identifiable.

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 no guidance on when to use this tool versus alternatives like restart or pause. No mention of prerequisites, conditions, or exclusions. The agent has to infer usage from the name alone.

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