kitty_goto_layout

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

No annotations are provided, so the description carries the full burden. It discloses valid layouts and option syntax (e.g., 'tall:bias=70'), but does not detail side effects, permissions, or failure modes. Adequate for a straightforward action.

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 focused sentences with no extraneous information. Front-loaded with the core action and immediately followed by key details (valid layouts, options). Efficient.

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?

Given no output schema and simple functionality, the description is sufficient. It covers the action, valid inputs, and optional parameters. No major gaps for an agent 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%, but the description adds value beyond the schema by listing valid layout names and explaining option syntax after a colon, which helps the agent understand parameter formatting.

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 ('Switch to') and resource ('window layout in active or specified tab'), and lists valid layouts, clearly distinguishing it from siblings like 'kitty_last_used_layout' and 'kitty_set_enabled_layouts'.

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?

The description states the tool is for switching layouts in the active or specified tab, providing clear context. It lacks explicit 'when not to use' or alternative suggestions, but the context is sufficient for its simple use case.

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