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

Annotations already declare destructiveHint=true, readOnlyHint=false, and openWorldHint=true, so the agent knows this is a destructive write. The description adds nothing beyond that: it does not say whether the deletion is permanent, whether sent digests or history survive, or whether confirmation/auth is required. For a destructive tool, that is a meaningful gap.

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?

A single short sentence, front-loaded and free of waste, but its brevity comes from under-specification rather than discipline.

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?

With no output schema, a destructive annotation, and an undocumented id parameter, the description should explain the effect of stopping (permanent? reversible?), the id's meaning, and how to locate it via list_schedules. None of that is present, so it is incomplete for a destructive mutation.

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?

One required parameter with 0% schema description coverage; the description never clarifies that 'id' is the schedule identifier (as opposed to a digest id or artifact id) nor its format. The description does not compensate for the schema gap.

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 sentence 'Stop a scheduled digest' is essentially the title restated with a verb ('stop') and the resource ('scheduled digest'). It does convey the action, but adds no scope, no distinction from siblings like schedule_digest or list_schedules, and is one step above a tautology.

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?

No guidance on when to use this versus schedule_digest (pause/resume vs. cancel?) or list_schedules to find the id. No prerequisites, no mention of what happens to already-sent digests.

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