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

Annotations already declare destructiveHint=true and idempotentHint=true, so the safety profile is covered. The description nonetheless adds real information beyond them: deletion is permanent and it cancels all future scheduled runs, which clarifies the blast radius. It omits what happens if the taskId is invalid or whether confirmation is expected.

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, zero filler, and the irreversible nature is front-loaded in the leading adverb before the routing hint.

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 rich annotations and no output schema, the definition covers purpose, effect, and when to use it. Minor gaps remain around failure behavior (task not found) and whether an explicit user confirmation is required before calling.

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?

There is a single parameter with 100% schema description coverage ("ID of the scheduled task to delete"), so the schema fully documents it. The description adds nothing about the taskId itself (format, where to get it), which is the expected baseline 3 when the schema does the work.

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 and resource ("Permanently delete a scheduled Replo task") plus the effect ("stop all future runs"), which makes it trivially distinguishable from read-side siblings like get_task and list_tasks as well as the other delete_* tools.

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 an explicit when-to-use condition: "Use this when the user no longer wants a scheduled prompt to run." It does not name a when-not case (e.g., temporarily pausing vs. deleting) or mention checking the task first via get_task/list_tasks, so it stops short of a full routing statement.

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