create_codebuddy_session

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

No annotations are provided, so the description carries the behavioral burden. It discloses that the process is not started and starts lazily on the first prompt, which is useful. However, it does not mention side effects, persistence, or what the return value is (though an output schema exists), leaving gaps in behavior disclosure.

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 three sentences long, front-loads the primary purpose, and includes a specific usage tip for ssh mode. There is no redundant wording, and every sentence adds value.

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 tool with 11 parameters and no schema descriptions, this description is far too sparse. It does not explain the required cwd parameter, the meaning of most parameters, or how this tool fits into the session lifecycle (e.g., that it must be called before prompt_codebuddy). The output schema exists but the description does not guide the agent on constructing a valid call.

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?

With schema description coverage at 0%, the description must explain parameters, but it only touches on launch_mode, providing context for the 'ssh' value. The other 10 parameters (cwd, env, ssh_args, ssh_host, etc.) are left unexplained, so the agent has no semantic guidance for them.

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 clearly states it configures an isolated CodeBuddy ACP session without starting the process, a distinct action from siblings (close, prompt, respond, cancel). The verb 'configure' and resource 'session' are specific, and the clarification about not starting the process adds precision.

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 explicit guidance for the ssh launch mode, telling the agent to use launch_mode='ssh' for remote execution. However, it does not explicitly state when to use this tool versus its alternatives, though its role as a creation/configuration step is implied by the name and sibling lifecycle actions.

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