Resize terminal

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

Annotations already declare readOnlyHint=true and openWorldHint=false, covering the safety profile. The description adds useful context by clarifying this is a metadata-only store with no PTY ioctl, which explains why the operation is side-effect-free; however, it does not describe result contents beyond what the existing output schema already provides.

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?

A single 8-word sentence with a parenthetical caveat that carries critical scope information. Every word earns its place and the key limitation is front-loaded.

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 simple 3-parameter tool with an output schema and annotations, the description is mostly adequate, but it omits valid value ranges for cols/rows and the trigger context for when dimensions should be stored. These gaps are non-fatal given the tool's simplicity, but a fuller description would include them.

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 0%, so the description must compensate, but it only maps 'terminal dimensions' to cols/rows and says nothing about session_id, which is the required parameter. The parameter names and defaults (80, 24) are self-explanatory, but the description does not fully fill the gap left by the schema.

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 uses a specific verb and resource ('Store terminal dimensions') and the parenthetical 'no PTY ioctl yet' scopes the behavior precisely, preventing an agent from expecting an actual resize effect. It distinguishes this tool from the terminal_* siblings by clarifying it only stores metadata, though it does not explicitly name an alternative.

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?

There is no explicit guidance on when to call this tool versus terminal_create, terminal_write, or terminal_signal, and no when-not-to-use conditions. The 'no PTY ioctl yet' caveat implies a limitation but does not route the agent to an alternative or describe the triggering context (e.g., after a window resize event).

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