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

Annotations already declare this a safe read (readOnlyHint=true, destructiveHint=false), and the description still goes well beyond them: it discloses that secrets in `args` are redacted, that events under non-integer cron keys are silently omitted, that `malformed_timestamps` and `cron_disabled` are surfaced as flags, and it defines `overdue` and negative `seconds_until_run`. That is substantive behavioral context an agent cannot get from the annotations.

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?

Purpose is correctly front-loaded, and most of the length is earned by the inline return-shape documentation (there is no output schema). However, the single dense run-on paragraph is hard to scan, and the final sentence is garbled/truncated ('core's md5 of … Through Royally: its server marks it read-only, so it runs straight away'), which is dead weight and confusing.

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 annotation coverage of results, the description supplies the full return contract -- every field of `events`, the envelope counters, and the edge-case flags -- plus how past-due events are represented. An agent could parse and act on this output without ever seeing a response.

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 coverage is 100%, so the baseline is 3, but the description adds real meaning on top: it explains the paging contract between `offset`, `returned`, and `total`, which the schema does not express. It does omit `site_id` entirely, keeping it from a 5.

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?

Opens with a precise verb+resource+ordering: 'List scheduled WP-Cron events, soonest first.' No other tool in the mcp-easy-ai namespace lists cron events, so there is no sibling confusion, and the ordering guarantee is stated up front.

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 gives one piece of procedural guidance -- how to page past the 500 cap by keeping `hook` fixed and advancing `offset` by `returned` -- but never says when to reach for this tool versus adjacent tooling or what to do when the list is empty or cron is disabled. Usage is implied rather than framed as when/when-not.

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