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

Annotations already declare destructiveHint=true and openWorldHint=true, but the description adds genuine behavioral context beyond them: the returned agent answer plus replay_url recording, multi-minute runtimes, persistent browser sign-in between jobs, and consumption of the user's MyClawn plan. It does not clarify reversibility or failure/partial-completion behavior for a destructive open-world action, keeping it from a 5.

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 definition is front-loaded with what the tool is, then moves to usage and return behavior. Every sentence carries information, though the dense enumeration of use cases makes it longer than strictly necessary for an experienced agent.

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?

An output schema exists, yet the description still surfaces the user-facing replay_url and the multi-minute latency that an agent must communicate. Combined with the message-briefing guidance and plan-usage note, nothing an agent needs to select and invoke this tool correctly is missing.

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 100%, so the schema already documents both parameters, establishing a baseline of 3. The description does add briefing guidance for 'message' ('write the task the way you would brief a contractor ... include only what the task needs, not the conversation'), but the 'private' parameter is never mentioned in the description text, so value beyond the schema is marginal.

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 states a specific verb and resource ('Hand a job to the user's own MyClawn computer'), which is far more than a restatement of the name. It enumerates concrete job types (signed-in browsing, email, forms, file editing, long-running tasks), making the capability unambiguous. It does not, however, explicitly differentiate itself from the sibling read/utility tools (activity, status, tasks), so it stops short of a 5.

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?

It gives clear when-to-use guidance: 'Use it for what you cannot do from this chat', followed by specific scenarios. This establishes a positive selection rule and an implicit exclusion (things doable from chat). It does not name alternative sibling tools or state when another tool would be preferable, so no explicit alternative routing is present.

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