Resize a terminal session

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

Annotations already declare readOnlyHint=false, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds that resizing affects the tmux window/PTY of a named session, which is useful beyond the annotations, but it does not say what happens to output or programs already running in the session, nor whether the session must already exist.

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 tight sentences with zero filler; the core action is front-loaded and the usage hint follows. Nothing could be removed without losing information.

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?

All parameters are documented and annotations cover safety and idempotency, so the basics are present. For a tool that mutates a live PTY, however, the description omits what happens to in-flight output or running applications and whether a nonexistent session errors, leaving it adequate but with clear gaps.

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 all three parameters carry both descriptions and value bounds, so the schema does the heavy lifting. The description adds no syntax, format, or defaults beyond what is already structured.

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 verb and resource: resizing the tmux window/PTY backing a terminal session. It is clearly distinct from sibling tools like terminal_create, terminal_write, and terminal_read. It stops short of explicitly naming how it differs from those siblings, but the action is unambiguous.

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?

"Useful before launching TUI programs" gives an explicit, actionable usage context rather than leaving it implied. There are no exclusions or when-not-to-use conditions, and no mention of how to discover current dimensions before resizing.

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