wordpress_advanced_cron_list

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

No annotations provided, so description carries full burden. It discloses return content (schedule, next run time, arguments) which compensates for missing output schema, but omits safety confirmation (read-only status), pagination, or error behaviors.

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 structure is efficient and front-loaded, though the '[UNIFIED]' prefix adds noise without conveying actionable information for tool selection.

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?

Adequate for a simple read operation with no nested objects, and describing return values substitutes for missing output schema. However, the undocumented 'site' parameter creates a critical gap for invocation.

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 0% for the single 'site' parameter. Description fails to compensate—it offers no guidance on parameter semantics (e.g., whether 'site' expects URL, ID, or slug), leaving the parameter effectively undocumented.

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?

Specific verb 'List' + resource 'WordPress cron jobs' + scope 'all scheduled'. Clearly distinguishes from sibling 'wordpress_advanced_cron_run' (execution vs listing).

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?

Implied usage through naming and verb choice (list vs run), but lacks explicit when-to-use guidance, prerequisites, or conditions for choosing over alternatives.

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