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

Annotations already declare readOnlyHint=false, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds useful context ('No launch', the isPrototype requirement tied to url), but does not explain mutation effects, revision handling, or what happens to existing tasks. Moderate added value over annotations.

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?

Front-loaded and compact, with the core action stated first and rules following. Sentence fragments ('No launch.') are efficient rather than wasteful, though 'Flat fields; no configuration object' borders on cryptic without explanation of what configuration would otherwise be.

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, so return values need not be explained. However, with 9 parameters including three required identifiers (testId, expectedRevision, blockId) and 0% schema coverage, the description is not complete enough to reliably construct a call. It covers the differentiating fields but omits mandatory and optional semantics.

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% across 9 parameters, so the description carries the full burden. It explains url, isPrototype, and 'wording' (task), but leaves testId, expectedRevision, blockId, position, scenario, and stopCondition entirely undocumented. Roughly two-thirds of parameters get no semantic help.

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 ('add') and resource ('task') with clear scope ('to an existing draft'), and distinguishes itself from edit_draft_advanced by noting 'flat fields; no configuration object'. It clearly signals it is not a launch operation, separating it from launch_test. Sibling differentiation is present though not exhaustive.

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 contextual rules ('Omit wording only for an intentionally incomplete draft') and an explicit alternative ('Use find_operations for prototypes or advanced settings'), plus a scoping statement ('No launch'). This approaches when/when-not guidance, though it never states prerequisites like draft revision state or permissions.

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