iyke_session_start_in_project

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

With no annotations, the description discloses key behaviors: lazy subprocess spawning on first prompt, initial_prompt being informational only. It clearly indicates a write operation (creation). Could additionally mention side effects or constraints.

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 four sentences long, each sentence contributes unique information. No fluff, front-loaded with purpose.

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 low schema coverage, the description explains return value (thread_id), parameter behavior (cwd default, initial_prompt limitation), and lifecycle (lazy spawn). Lacks explicit definition of project_id, but overall adequate.

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 33% (only cwd described in schema). The description adds important context for initial_prompt (informational only) and implies project_id meaning, but does not explicitly describe project_id. It adds moderate value beyond 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 'Mint' and resource 'new Claude chat thread attached to a project', clearly distinguishing it from sibling session tools like iyke_session_list and iyke_session_move.

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 provides clear context: after creation, use acp_prompt or open session UI. It also notes that initial_prompt is currently not forwarded. However, it lacks explicit when-not-to-use or alternatives.

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