prepare_multi_agent_edit_task

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

With no annotations, the description must disclose side effects, but it only lists actions without explaining consequences. 'Lock multi-agent edit scope' is vague and does not clarify whether this is reversible, requires a clean working directory, or modifies git state. Potential side effects of branch creation and screenshots are not elaborated.

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, front-loaded with action verbs. It is extremely concise and every word contributes to understanding the core function.

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?

Given the tool's complexity (4 params, no output schema, no annotations), the description is incomplete. It does not explain the multi-agent scope locking mechanism, prerequisites, or how this tool fits with validate_multi_agent_edit and finalize_multi_agent_edit. The description leaves critical operational details unspecified.

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%, and the description does not reference any of the four parameters. It gives no guidance on how 'instruction', 'agents', 'pathname', or 'createPreview' affect the actions. This adds no value beyond the raw schema.

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 three specific actions: creating a branch, capturing before screenshots, and locking multi-agent edit scope. It distinguishes itself from siblings like create_task_branch and prepare_website_edit_task by explicitly focusing on the multi-agent edit scope.

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 this tool is used at the start of a multi-agent edit workflow, but it does not explicitly state when to use it versus alternatives like prepare_website_edit_task or finalize_multi_agent_edit. No exclusion criteria or prerequisites are mentioned.

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