grok_session_create

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 does disclose that the tool creates a session and returns a sessionId, but it does not explain the surprising yoloMode default of true (auto-approve tool permissions) or any downstream effects of session creation. The schema documents the default, but the description adds little beyond the mutation and return value.

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?

A single sentence that front-loads the verb and purpose, names the endpoint, and states the return value. Every word earns its place with no filler.

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 tool with a fully documented schema, the description covers the essential call semantics and return value. However, with no output schema and no guidance on session lifecycle relative to grok_session_load, an agent is left to infer when a new session is needed versus loading an existing one.

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 description coverage is 100%, so the baseline is 3. The description adds no parameter-level detail; both cwd and yoloMode are already well-documented in the schema with meanings and defaults. The description neither compensates for gaps nor repeats schema, so baseline applies.

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: 'Create a new ACP session on the local Grok Build agent (session/new).' This clearly distinguishes from siblings like grok_session_load, grok_prompt, grok_cancel, and grok_status, and even names the underlying endpoint.

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 implies the use case (creating a fresh session) but gives no explicit guidance on when to use this tool versus grok_session_load for existing sessions, nor any mention of prerequisites. There is clear context but no exclusions or alternatives beyond what the name conveys.

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