focus_warp_session

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

With no annotations, the description carries the full behavioral burden. It discloses the prerequisite UUID source and an important invalid-input case, but does not explain what focusing does to the active pane, what happens when the UUID is not found, or whether Warp must be running.

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?

Three sentences, front-loaded with the action, followed by valid UUID sourcing and the invalid alternative. Every sentence earns its place.

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 one-parameter focus tool with no output schema and no annotations, the description covers the action, valid input source, and a key invalid-input warning. It could be more complete by stating the effect on pane focus or failure behavior, but it is sufficient to invoke correctly.

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 baseline is 3. The description adds meaning beyond the schema by specifying that the UUID must be Warp-recognised and typically comes from the shell shim, while locally-minted UUIDs from open_terminal_tab are invalid.

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 states a specific verb and resource: 'Focus an existing Warp pane by its session UUID.' It also explicitly distinguishes the valid UUID source from the locally-minted UUIDs returned by open_terminal_tab, so an agent can tell this apart from related session tools.

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?

It gives clear usage conditions: the UUID must be one Warp itself recognises, typically from the shell shim's OSC 777 event, and locally-minted UUIDs from open_terminal_tab are not valid. It does not explicitly contrast this with siblings like send_to_session, but the exclusion of open_terminal_tab UUIDs is strong guidance.

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