Ambient Code Platform MCP Server

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

Without annotations, description carries full burden and successfully discloses stateful behavior (token stored in memory) and validation logic ('verifies it works'). Missing error behavior or persistence scope keeps it from 5.

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 precise sentences: first establishes purpose, second declares side effects. Zero redundancy, appropriately front-loaded.

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?

Sufficient for an authentication tool with no output schema; explains mechanism and runtime side effects. Minor gap regarding behavior when optional token parameter is omitted.

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 100%, establishing baseline 3. Description mentions 'Bearer token' reinforcing the token parameter's purpose but adds minimal semantic detail beyond what the schema already provides for the cluster parameter.

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?

Uses specific verb 'Authenticate', identifies resource 'cluster', specifies mechanism 'Bearer token', and discloses side effects 'Sets the token in memory'. Clearly distinguished from session management siblings like acp_list_clusters or acp_switch_cluster.

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?

Implies usage context through side effect description ('Sets the token in memory'), but lacks explicit guidance on when to invoke versus sibling acp_switch_cluster or prerequisites for other cluster operations.

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