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

The description goes well beyond the destructiveHint annotation by specifying exactly what can be destroyed: enable/resume may execute pending refinement that DELETES tasks, and process_now may start an intake batch. It also warns that destructive effects can occur even when the echoed scheduler state looks unchanged, and clarifies the gate returns a typed reason/recovery step instead of a spawn promise.

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 purpose line is front-loaded and the bullets are efficient, with no filler around the operations. A few phrases like 'spawn promise' and 'dev scheduler switch' assume internal familiarity, which keeps it from a 5.

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 tool with a rich annotations block and an output schema, this covers the action semantics, destructive side effects, and return state. It does not discuss permissions, idempotency, or project existence, but none of those are implied as required by the schema or annotations.

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?

With schema coverage at 0%, the description carries the burden; it fully defines the action values and their distinct effects. project_id is only implied by 'a project's autonomous work,' but as one of the two required fields it needs no deep explanation.

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 opening sentence names a specific verb set—start, pause, resume—with a clear resource ('a project's autonomous work'), and the bullet list disambiguates four action modes. It does not explicitly differentiate from sibling tools such as project_status or refine_request, 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?

The action bullets give concrete conditions: enable/disable govern scheduler_enabled for active projects, resume clears peak/backoff/manual pauses, and process_now applies independently of the dev scheduler switch. This is solid context for choosing an action, though it never names a sibling as the alternative, so there are no exclusions.

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