Start Figma Slides Session

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

With no annotations present, the description carries the burden of disclosing behavior. It states that the tool starts a server, waits for a plugin connection, and returns status/instructions if not connected. This is a meaningful disclosure of the tool's side effects and outcome, though it omits lifecycle details like how to stop the server or timeout behavior.

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 two sentences, immediately states the core action, and includes trigger phrases and return behavior. Every sentence earns its place with no filler.

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 zero parameters and no output schema, the description covers the essential context: what the tool does, when to call it, and what it returns. This is complete for a simple startup tool and does not require additional detail.

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?

The tool has zero parameters, so the schema is empty and the baseline is 4. The description does not need to explain parameter semantics, and the 100% schema coverage confirms there are no undocumented parameters.

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 a specific action: 'Start the WebSocket server and wait for the Figma plugin to connect.' This distinguishes it from sibling tools like connection_status, which likely only checks status rather than initiating a session.

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?

It provides explicit trigger phrases: 'Call this when the user says "start figma session", "connect to figma", or "open slides".' This is clear usage guidance, though it does not explicitly name alternatives or when not to use it, such as distinguishing from connection_status.

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