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

Annotations only cover the safety profile (readOnlyHint=false, destructiveHint=false, idempotentHint=false), so the description adds genuine value: the auth requirement (config:write), the SHIP API dependency with a docs link, and the key behavioral fact that firing files an ordinary tracker issue rather than spawning a separate execution mode. It does not address the non-idempotent hint (duplicate tasks on retry), which is a notable omission.

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?

Three sentences, each load-bearing, with the core purpose front-loaded before the mechanics and the API/capability footnotes. The middle sentence is dense but the parenthetical aside about execution mode is worth the words; minor tightening is possible.

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 12-parameter mutation with no output schema, the description covers the conceptual model, auth requirement, and downstream side effect, which is what an agent needs to invoke it correctly. It omits retry/duplicate behavior and does not point at get_scheduled_task or list_scheduled_tasks for verification.

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% with 12 well-documented parameters, including conditional requirements (weekday for weekly, dayOfMonth for monthly) and the label-must-already-exist caveat. The description adds no parameter-level detail beyond the schema, so the baseline of 3 applies.

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?

Opens with a specific verb and resource ("Create a recurring agent mission") and immediately clarifies the conceptual model: a stored mission request, not a new execution mode. It also distinguishes itself from run_scheduled_task by explaining that firing is what produces the tracker issue and pipeline run.

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 routes the agent between this tool and run_scheduled_task (immediate firing) and states the required config:write capability, which is real usage guidance. It stops short of explicitly naming when not to use this versus update_scheduled_task or create_mission, so it is clear but not exhaustive.

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