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

Annotations already declare destructiveHint=true, readOnlyHint=false, openWorldHint=true and idempotentHint=false, so safety is covered; the description still adds real behavior beyond them — that the fire is NOT published, that it targets the latest draft by default, that it runs the version's workflow, and that the run is captured in FULL with output and traces intact unlike an automatic fire. It does not cover permissions or rate limits, hence not a 5.

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-loads the core action and its key constraint (without publishing) in the first clause, then layers on the return-value handoff and the full-capture nuance. It's dense but every sentence carries distinct information; only the parenthetical sibling reference is slightly gratuitous.

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 destructive, open-world mutation tool this covers purpose, side-effect warning, draft-vs-published scope, version selection, and the resolution path to get_workflow_run. With an output schema present, no return-value explanation is owed, so nothing material 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% and already documents slug vs schedule_id and the version-omit-for-latest behavior. The description restates the version semantics ('omit version for the latest draft') without adding format or precedence detail, so baseline 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?

States a specific verb (fire a schedule once, immediately, without publishing) and immediately differentiates from publish_schedule and preview_dynamic_endpoint by name. An agent can tell exactly what distinct operation this is relative to run_workflow or publish_schedule.

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?

Gives explicit when-to-use cases: testing a draft before it goes live, and reproducing a firing that was only sampled when it fired automatically. It names the contrasting operations (publish, automatic fire, preview_dynamic_endpoint) and points to get_workflow_run for the outcome, so the agent knows both when to call it and how to follow up.

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