wordpress_unschedule_event

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

No annotations are provided, so the description carries full burden. 'Remove' implies a destructive mutation, but it doesn't disclose whether this requires admin permissions, if the removal is permanent/reversible, what happens to associated data, or error conditions (e.g., if hook doesn't exist). Some behavioral context is missing for a mutation tool.

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?

Single sentence, zero waste, front-loaded with the core action. Every word earns its place without redundancy or unnecessary elaboration.

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 mutation tool with no annotations, no output schema, and 0% schema description coverage, the description is inadequate. It lacks behavioral context (permissions, reversibility), parameter guidance, and expected outcomes, leaving significant gaps for an agent to use it correctly.

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 0%, but the description doesn't add any parameter details beyond implying 'hook' is needed. It doesn't explain what a 'hook' is, format examples, or where to find valid hooks. With 1 parameter and no schema descriptions, baseline 3 is appropriate as the description at least implies the parameter's role.

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 ('Remove') and target ('a scheduled cron event'), providing specific verb+resource. However, it doesn't distinguish from potential siblings like 'wordpress_list_cron_jobs' or 'wordpress_schedule_event' beyond the obvious difference in action direction.

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 tool versus alternatives is provided. The description doesn't mention prerequisites (e.g., needing to know the hook name from listing cron jobs) or when not to use it (e.g., for unscheduled events).

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