create_direct_session

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

Annotations indicate a write operation (readOnlyHint: false) and not destructive. The description adds the prerequisite of enableDirectProfile: true, which is useful, but it doesn't disclose what creating a session does (e.g., whether it changes files, what session state occurs). With annotations present, the bar is lower, and this description provides only marginal additional context beyond them.

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 sentences, each earning its place. The first states the action and purpose, the second states a critical prerequisite. No fluff, properly 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 3-parameter creation tool with no output schema, the description covers the basic purpose and prerequisite but omits workflow context such as what the session enables, how it connects to direct patching, and what the return value is. Given sibling tools like finalize_direct_session and request_direct_review, a bit more context would help.

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 100%, so the baseline is 3. The description mentions the config requirement but doesn't add any detail about the parameters themselves (title, repo_path, expected_changes) beyond their schema descriptions. It neither helps nor hurts.

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 the tool creates a 'Direct editing session' for applying patches directly, which is a specific verb+resource combination. However, it doesn't explicitly distinguish this from sibling tools like request_direct_review or create_task, so it stops short of full differentiation.

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 gives minimal usage context: it says the session is for ChatGPT to apply patches and requires enableDirectProfile: true, but doesn't explain when to prefer this over alternatives or when not to use it. No exclusions or alternative references are provided.

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