edits_insert

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

The description discloses that the tool returns an edit id and expiry and that it opens a session. However, it does not discuss potential behaviors like session limits, permissions, or error handling (e.g., if a session already exists). Given no annotations, the description carries full burden and is adequate but not rich.

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 with no fluff. The first sentence states the action and result, the second adds a crucial usage note. Every word earns its place.

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 single-parameter tool with no output schema, the description covers the purpose, return values, and relationship to siblings. It lacks detail on the expiry format, but overall it is sufficient for an agent to use correctly.

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 schema already provides a clear description of the single parameter (packageName). The tool description adds no additional meaning beyond the schema, and schema coverage is 100%, so baseline 3 is appropriate.

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 'Open a new edit session for an app' with a specific verb and resource, and it distinguishes from sibling tools like edits_commit or edits_delete by focusing on session initialization.

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 use at the start of editing and mentions that subsequent edits.* tools need the returned id, providing clear context. It does not explicitly list alternatives, but the sibling list makes it obvious this is the first step.

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