create_session

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

No annotations provided, so the description must disclose behavioral traits. It mentions saving git context but does not explain side effects (e.g., modifies local repo?), required permissions, or whether the session is persistent. The description is insufficient for a tool with no annotation support.

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 a single sentence, which is concise but lacks necessary detail. It front-loads the verb but omits important context. Given the complexity (6 parameters), this is under-specified rather than effective conciseness.

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?

With 6 undocumented parameters, no annotations, and no output schema details (though output schema exists), the description is completely inadequate. It fails to explain core concepts like 'session', 'git context', or how parameters relate to functionality. The agent cannot correctly invoke this tool based on the description alone.

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 0%, meaning the input schema contains no parameter descriptions. The tool description does not explain any of the 6 parameters (e.g., project_id, interface, model_name, owner_id, repo_path, current_goal). The agent gets no guidance on what these parameters mean or how to use 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 states the tool creates a session and saves git context. This is a specific verb+resource, but the term 'git context' is vague. It broadly distinguishes from sibling tools (e.g., create_project, capture_project_memory), but lacks precision on what 'session' means in this context.

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?

No guidance on when to use this tool versus alternatives such as create_project, resume_project, sync_session_state, or load_unified_context. There is no mention of prerequisites (e.g., does a project need to exist?) or exclusions.

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