prepare_website_edit_task

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

With no annotations, the description carries the full burden of behavioral disclosure. It only states that the tool 'creates and prepares a scoped website edit task' without explaining what preparation involves, whether it modifies files or branches, or any side effects. The behavior is opaque, which is inadequate for a tool that likely orchestrates other actions.

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 concise, composed of a single sentence with no redundancy. However, its brevity comes at the cost of substance—it is too short to convey the operation's scope or nuance. It earns its place by being concise, but the content is minimal.

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, no annotations, and involves 4 parameters with a specific workflow context. The description is far too sparse to be complete; it does not explain what 'prepare' means, how it relates to subsequent tools like finalize_website_edit_task, or what outputs or state changes to expect. For a task-preparation tool, this is insufficient for an agent to use it 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?

Schema description coverage is 0%, and the description adds no information about the parameters. It does not explain the purpose of 'instruction', 'outputMode', 'targetPage', or 'approvedProtectedChanges', leaving the agent to rely solely on the schema names and defaults. This is below the baseline expected when schema coverage is low.

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 uses the verb 'Create and prepare' with the resource 'scoped website edit task', clearly indicating the tool's function. However, it does not explicitly differentiate from sibling tools like prepare_landing_page_task or prepare_multi_agent_edit_task, which could cause some ambiguity in tool selection.

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?

There is no guidance on when to use this tool versus its siblings or other tools. The description provides no context about the intended workflow, prerequisites, or cases where this tool is preferable to alternatives. With many related prepare_* tools among siblings, this lack of guidance is a notable gap.

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