Quickstart instructions

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

With no annotations provided, the description carries full responsibility for behavioral disclosure. It states that the tool returns a how-to, implying a read-only operation with no side effects, but does not explicitly confirm that it modifies no tmux state or require permissions. This is adequate for a simple help tool but not richly detailed.

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 a single, front-loaded sentence that directly communicates the tool's function without any wasted words. It is appropriately concise for the simplicity of the tool.

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 no parameters and no output schema, this description is complete. It tells the agent what the tool returns (a how-to) and its purpose (safe usage of tmux tools). The 'safely' qualifier adds useful context, and no additional details are necessary for such a straightforward meta-tool.

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 with an empty schema, so the baseline for parameter semantics is 4. The description adds no parameter information, but none is needed given the tool has no inputs.

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 the tool returns a concise how-to for using tmux MCP tools safely, with a specific verb and resource. It distinguishes itself from sibling tmux commands by being a meta-tool for instructions rather than a direct tmux operation.

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?

The description provides no explicit guidance on when to use this tool versus alternatives. It does not mention usage context, prerequisites, or when not to use it. The agent must infer that it is for getting started, but the description itself lacks this direction.

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