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

The annotations already establish that this is a non-read-only, non-destructive, closed-world operation, and 'start' is consistent with readOnlyHint=false. The description adds useful workflow context about frozen tasks and jobId handling, but it does not describe permissions, idempotency, side effects, or when startToken is needed.

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 front-loaded with the core action and uses only three short sentences. Every sentence adds routing or scoping value, with no repetition or filler.

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 two-parameter start tool with annotations and an output schema, the description covers purpose, allowed task IDs, and key alternatives well. The main residual gap is the unexplained optional startToken parameter.

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%, so the description must carry parameter meaning. It clarifies the taskId values by saying they are frozen tasks and listing the allowed options, but it does not explain the optional startToken parameter at all.

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 names a specific verb and resource: start a frozen task. It lists the exact task identifiers and distinguishes the tool from plan_task and job_status, so an agent can identify its purpose without opening the schema.

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 explicit exclusions — not for SEO, URLs, or ship-gate — and names the correct alternative, plan_task. It also states that agents with an existing jobId must use job_status, which directly resolves a likely routing ambiguity.

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