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

Annotations already include destructiveHint: true, so the destructive nature is declared. The description goes beyond by explaining 'no undo and no trash,' safety steps (recreate with create_schedule), and impacts on other resources: 'Documents already produced by past firings are unaffected and remain available through list_renders.' No contradiction with annotations.

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?

The description is concise (3 sentences plus return info) and front-loaded with the core purpose. Every sentence adds value: deletion behavior, undo mechanism, pause alternative, and effect on documents. Slightly longer than needed for the return value detail, but still efficient.

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?

Given the tool's simplicity (single parameter, no output schema, annotations present), the description fully covers what an agent needs: what it does, safety warnings, alternative actions, and return behavior. No gaps remain.

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?

The input schema covers 100% of parameters with a description for schedule_id. The description adds value by stating the return format '{ deleted: true }, or 404 if the id does not belong to this account' and referencing how to obtain the id from create_schedule or list_schedules, which is useful context beyond the schema.

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 description explicitly states 'Permanently delete a recurring schedule so it stops firing,' using a clear verb (delete) and resource (schedule). It differentiates from sibling tools like create_schedule and list_schedules by explaining what it does uniquely.

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?

Provides explicit when-to-use guidance: 'confirm with the user before calling this on a schedule you did not just create.' It also clearly states when not to use it: 'If the intent is only to pause it, do not use this tool,' and offers an alternative (enabled flag via REST). This covers exclusions and alternatives comprehensively.

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