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

Annotations already declare readOnlyHint=true, idempotentHint=true and destructiveHint=false, so the safety profile is covered. The description adds a genuinely useful non-annotated trait: the tool returns literal command text ('Exact tmux commands') rather than performing actions, which matters because there is no output schema. It does not say what happens when the requested task is outside the listed set.

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?

One front-loaded sentence with the core purpose first and the coverage list after; every clause maps to a real capability. The enumeration is long but it functions as a matchable capability list rather than 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?

For a single-parameter reference tool with full schema coverage, annotations, and no output schema, the description covers purpose, output form, and task scope adequately. The only meaningful omission is the fallback path when a task falls outside the enumerated set, which would be cheap to state.

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 100% and the single 'task' parameter already carries a concrete example ('detach without killing the agent'). The description's task list broadly mirrors that parameter's intent but adds no formatting, phrasing, or specificity guidance beyond the schema. Baseline 3 applies.

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 specific resource and output form: 'Exact tmux commands for common tasks', then enumerates the covered task areas (attach, detach, scrollback, mouse, panes). An agent can tell this is a task-to-command lookup rather than an executor. It does not explicitly differentiate itself from generate_tmux_conf or troubleshoot_connection, leaving that inference to the caller.

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?

Usage is implied by 'for common tasks from a phone', which hints at quick, on-the-go reference lookups. There is no explicit when-to-use statement and no exclusions or routing to siblings (e.g., 'for editing your tmux.conf use generate_tmux_conf', 'for broken connections use troubleshoot_connection').

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