Resize terminal

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

Annotations already declare it is a non-read-only, idempotent, non-destructive operation. The description adds meaningful behavior beyond that: it resizes both the PTY and the emulator and propagates change via SIGWINCH to running programs, which an agent cannot infer from annotations alone.

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 no filler. The core action is front-loaded, and the parameter behavior and propagation detail follow in service of the primary statement.

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?

No output schema exists, but for a resize tool the critical behavioral facts (partial update semantics, dual PTY/emulator resize, SIGWINCH propagation) are covered. Minor gaps remain around error conditions for invalid sessions or out-of-range sizes, though the schema bounds cols/rows.

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%, so the schema already documents cols, rows, and sessionId fully. The description restates the omit-to-preserve semantics already present in the schema, adding no new syntax or format detail. 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 verb and resource ('Change the terminal size'), which an agent can immediately distinguish from siblings like terminal_read or terminal_type. The scope is precise and 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?

Explains the partial-update behavior (omitting cols/rows preserves current values), which is useful contextual guidance. However, it gives no when-to-use or when-not-to-use signals relative to alternatives such as terminal_reset or terminal_create.

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