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

Beyond the annotations (readOnly/idempotent/non-destructive), the description adds real context: requires manage_options, runs synchronously ("runs straight away"), and sorts next-run ascending so overdue events surface first. It doesn't state whether all events are returned or if pagination exists.

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?

Front-loaded with purpose, then return shape, ordering, use cases, and permission requirement in a tight block. The "(site: demo.royalplugins.com)" parenthetical is redundant with the schema enum and slightly clutters the flow.

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?

With no output schema, the enumerated return fields (hook, next run unix/ISO, seconds until, is_overdue, recurrence, args) plus ordering give an agent enough to interpret results. Only completeness of the listing (volume limits/pagination) is unaddressed.

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 single site_id parameter has 100% schema coverage including the enum description, so the schema already does the work. The description only restates which site is targeted, adding no new syntax or behavioral meaning.

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?

"Enumerate scheduled wp_cron events" gives a specific verb and resource and makes clear this is a read of the cron table. However, it never distinguishes itself from the similarly named sibling mcp-easy-ai__wp_list_cron_events, so an agent facing both still has to guess.

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 names concrete diagnostic scenarios (missed schedules, plugin cron conflicts, unfired hooks) that tell the agent when this tool is the right pick. It stops short of stating when-not-to-use or naming an alternative tool.

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