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

Beyond the readOnlyHint/idempotent annotations it discloses concrete behavior: hook arguments are excluded, count is the total but events is capped at 200, timestamps are UTC ISO 8601, and the call requires manage_options. It also notes the AlphaBridge forwarding scope, which matters for multi-site connections.

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?

It is a single dense paragraph, but the key facts (list, ordering, fields, cap, permission) are front-loaded and each clause carries content. Slightly over-packed with semicolons, which costs a point on readability rather than on waste.

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 and no parameters, the description carries the burden well: it defines both output fields, the 200-item cap against the total count, the timezone/format, and the permission requirement. An agent has everything needed to call and interpret it.

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 tool takes zero parameters, so the baseline is 4. The description usefully spends its words instead on the response shape (count, per-event next_run and schedule, with false for single events), compensating for the absent output schema.

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 ('List the WP-Cron events scheduled on this site') plus ordering ('soonest first') and the exact fields returned per event. It is clearly distinguishable from the mutation siblings wp_schedule_cron and wp_unschedule_cron, which it names.

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 explicit usage context ('Useful to check whether a job runs and when') and points to the tools that add and clear events, so an agent can route correctly. It stops short of stating when-not to use it (e.g. use wp_unschedule_cron to remove instead of reading), so not a full 5.

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