jms_resize_terminal_session

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

With no annotations, the description carries full responsibility for behavioral disclosure. It only says 'resize,' which is a mutation, but does not describe effects, reversibility, session requirements, or whether it returns success/failure. This is a significant gap for a tool that alters an existing session.

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, tightly worded sentence. It is front-loaded with the verb 'resize' and wastes no words, making it easy to parse and directly informative.

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 tool, the description is minimally sufficient but lacks important contextual details like preconditions or behavioral notes. Since an output schema exists, return values may be covered there, but the description alone is thin given the absence of annotations and parameter descriptions.

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%, and the description does not elaborate on any parameters. While the parameter names (session_handle, cols, rows) are intuitive, the description fails to provide additional meaning or context, such as valid ranges or format details.

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 ('resize') and identifies a clear resource ('managed KoKo terminal session'), which distinguishes it from sibling terminal session tools like send_input or close_terminal_session. However, it does not explicitly mention the dimension parameters (cols, rows), though these are present in the schema.

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?

No guidance is provided on when to use this tool versus alternatives. There is no mention of prerequisites (e.g., an active session) or scenarios where resizing is appropriate. The description simply states what it does without any conditional context.

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