delete_auto_schedule

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

With no annotations provided, the description carries full burden. It states the tool deletes a schedule and requires a Premium plan, but lacks details on permissions, side effects (e.g., impact on scheduled posts), error handling, or confirmation steps. For a destructive operation, this is a significant gap in behavioral disclosure.

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 two concise sentences that are front-loaded with the core action and include a key constraint. Every word serves a purpose with no wasted text, making it highly efficient and easy to parse.

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 tool with no annotations and no output schema, the description is minimal. It covers the basic purpose and a plan requirement but misses critical context like what happens after deletion, error cases, or return values. Given the complexity, it's adequate but has clear gaps.

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%, so the schema already documents all parameters thoroughly. The description adds no additional parameter information beyond implying the 'title' parameter is used for deletion, which is redundant with the schema. Baseline 3 is appropriate as the schema does the heavy lifting.

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 clearly states the action ('Delete') and resource ('auto-posting schedule'), specifying it's done 'by its title'. It distinguishes from siblings like 'delete_post' or 'delete_comment' by focusing on schedules, but doesn't explicitly contrast with 'set_auto_schedule' or 'list_auto_schedules'.

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?

It mentions a prerequisite ('Requires Premium plan'), which provides some context for when to use it. However, it doesn't specify when to choose this over alternatives like 'set_auto_schedule' for modification or provide exclusions, leaving usage somewhat implied rather than explicit.

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