iyke_split

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

No annotations provided, so description carries the full burden. Discloses key behaviors: defaulting to focused pane, directional split, and a system cap. Lacks details on reversibility or permissions, but adequate for the tool's simplicity.

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 concise sentences with no filler. First sentence introduces action and optional parameter; second sentence clarifies direction semantics and constraint. Information 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 2-parameter split tool with no output schema, the description covers all critical aspects: purpose, parameter usage, direction semantics, and a system constraint. No gaps identified.

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?

Adds meaning beyond schema: explains pane_id default behavior ('Defaults to focused pane') and visualizes directional effects ('side-by-side' vs 'top-bottom'). Schema only provides enum for direction but no description; description compensates.

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?

Clearly states 'Split the focused pane (or a specific pane via pane_id) into two' with explicit directional meanings. Unambiguous verb-resource pair; no sibling tool duplicates this functionality.

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?

Provides a concrete constraint ('Subject to the in-app MAX_LEAVES cap (currently 6)') that guides when to use. Could explicitly state when not to use (e.g., when max leaves would be exceeded), but the cap is clearly mentioned.

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