wordpress_unschedule_event

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

With no annotations provided, the description is the sole source of behavioral disclosure. It only states the action 'Remove' without indicating that this is a destructive, irreversible operation, whether all occurrences of the hook are removed, or any permission requirements. Key operational context is missing.

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 a five-word sentence, front-loaded and free of any redundant content. It efficiently communicates the core purpose without wasted words, effectively earning its place.

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 that there are no annotations, no output schema, and a sparse input schema, the description leaves the agent without critical operational details: what the 'hook' parameter refers to, expected return values, failure handling, or side effects. This brevity is insufficient for reliable invocation, even for a simple tool.

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 schema has one required parameter 'hook' with zero description coverage, and the description does not mention it at all. It adds no meaning beyond the schema's bare type definition, failing to explain what a hook is, how to format it, or its role in identifying the event to remove.

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 'Remove a scheduled cron event' clearly identifies the action (remove) and the resource (scheduled cron event), distinguishing it from sibling tools like wordpress_schedule_event, wordpress_list_cron_jobs, and wordpress_run_cron. It is specific and unambiguous.

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 provides no information about when to use this tool versus alternatives, nor does it mention prerequisites such as listing cron jobs with wordpress_list_cron_jobs to find the exact hook name. There is no guidance on exclusions or behavior if the event does not exist.

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