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

Goes well beyond annotations by disclosing the skip-if-previous-open bypass, the guaranteed new-issue side effect even when a prior mission is open, and the exact authorization requirements (pipeline:control capability, missions:run scope for token callers). This is precisely the operationally important context annotations alone (readOnly/idempotent/destructive) cannot convey.

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 with the action and its key override, and every clause carries meaning. The second sentence is dense with em-dash asides about authorization, slightly reducing readability, but nothing is wasted.

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 mutation-triggering tool with no output schema, the description supplies the side-effect semantics and the full auth prerequisite set an agent needs before invoking. Nothing essential 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% for the single parameter, so the schema already documents scheduledTaskId. The description adds no format or sourcing detail for the id beyond what the schema states, so the baseline 3 is appropriate.

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?

States a specific verb (fire/run) and resource (scheduled task) with the key modifier 'immediately', and the 'bypassing its schedule' clause cleanly separates it from the passive scheduled execution that create/update_scheduled_task imply. An agent can distinguish this trigger action from its CRUD siblings at a glance.

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 description gives strong context on when this behavior applies (manual override of schedule and the skip-if-previous-open guard), which implicitly frames the manual-trigger use case. It stops short of naming a sibling alternative or an explicit when-not-to-use condition, so it lands just below a 5.

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