begin_edit_session

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

Annotations already mark destructiveHint=true; description adds 'short-lived' and authorization requirements as useful context. However, it does not explain session expiration behavior or the need to end the session, and it doesn't mention potential side effects of opening a write session.

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 concise sentences, front-loaded with the primary action and followed by prerequisites. No filler or repetition.

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?

The tool has no output schema, yet the description does not mention what the session returns (e.g., session ID) or how the session is used with sibling tools. It also lacks parameter semantics, making the description incomplete for effective invocation.

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?

The description makes no mention of the required 'justification' parameter. With 0% schema description coverage, the description fails to explain the purpose or content of the justification, leaving the agent to infer from the name alone.

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?

Specific verb 'Begin' with resource 'short-lived write session' clearly states the tool's function. It also distinguishes from siblings like end_edit_session and apply_memory_patch by establishing this as the session initiation step.

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?

Provides clear prerequisite context ('requires server write opt-in and native target authorization') but does not explicitly state when to use vs alternatives. The sibling end_edit_session implies the pairing, but no explicit 'use before write operations' guidance is given.

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