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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the safety profile is covered. The description adds genuinely useful extent-of-destruction detail: the saved workflow persists and an in-flight run completes — context the annotations cannot express and that materially affects an agent's decision to call it.

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?

Two short sentences, front-loaded with the action and identifier, then the consequences. No filler and nothing that could be dropped without losing meaning.

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 one-parameter destructive tool with annotations covering the safety profile and no output schema, the description supplies the key behavioral caveats. It is slightly thin on idempotency and how to source the scheduleId, but nothing critical 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 0% for the single parameter, so the description carries the burden; it names scheduleId and identifies it as the schedule reference, which is more than the bare uuid schema. However it does not say where to obtain a valid scheduleId (e.g., list_scheduled_workflows) or address behavior for unknown IDs.

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 ('Stop') and resource ('scheduled workflow') and is scoped by an explicit identifier. It implicitly distinguishes itself from the sibling delete_workflow by clarifying that the saved workflow itself remains, though it never names that sibling explicitly.

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 conveys scope (what is not affected) but offers no explicit when-to-use guidance and does not contrast itself with adjacent tools such as cancel_workflow or delete_workflow. Usage is inferable from the effect statements rather than stated.

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