Ambient Code Platform MCP Server

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

No annotations provided, so description carries full burden. Discloses two important behavioral constraints: target must be 'stopped' sessions and 'confirm=true' is mandatory. However, missing side effects (what happens to running sessions in the list?), error behavior, and whether operation is atomic or partial on failure.

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?

Two sentences with zero waste. Front-loaded with the core action followed by critical constraints. Every word earns its place; no redundant explanation of parameters already well-documented in schema.

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?

Adequate for a 4-parameter destructive operation lacking annotations or output schema. Covers the operation scope and safety prerequisite. Missing return value description (what indicates success?) and explicit differentiation from the numerous sibling bulk tools, which would help in this crowded namespace.

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?

Input schema has 100% coverage, establishing baseline 3. Description repeats the 'max 3' constraint already in schema and adds emphasis on the confirmation requirement, but does not add syntax details, example formats, or semantics beyond what the schema already provides clearly.

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?

Clearly states the action (restart), resource (sessions), and scope (multiple, max 3). Specifies 'stopped' sessions, which distinguishes from general restart operations. However, does not explicitly differentiate from sibling 'acp_bulk_restart_sessions_by_label' (explicit names vs label targeting).

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 constraint-based guidance (max 3, requires confirm=true) implying safety-critical usage, but lacks explicit guidance on when to choose this over the single 'acp_restart_session' or the label-based bulk variant. Usage is implied rather than stated.

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