wordpress_list_cron_jobs

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

With no annotations provided, the description must carry the behavioral disclosure burden. 'Get all scheduled WordPress cron jobs' implies a read-only operation and returns a list, but it does not disclose details like what fields are returned, whether the list is sorted, or any potential performance implications. This is a basic action description, adequate but not enriching.

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?

The description is a single, clear sentence with no filler or repetition. It is appropriately sized for a zero-parameter tool and front-loads the action verb.

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 simple list operation with no parameters and no output schema, the description is largely complete. It clearly states what is returned: all scheduled WordPress cron jobs. The lack of an output schema leaves some ambiguity about the exact structure, but this is a minor gap for selection and 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?

There are no parameters in the input schema, and the baseline for zero parameters is 4. The description complements this by specifying 'all' scheduled cron jobs, which implies no filtering, so there is nothing more to add.

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 uses the specific verb 'get' with the resource 'all scheduled WordPress cron jobs', clearly stating the tool's scope. This distinguishes it from sibling cron tools like schedule_event, unschedule_event, and run_cron, which perform different actions.

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 provides no guidance on when to use this tool versus alternatives. There is no mention of exclusions, prerequisites, or comparison with related cron tools such as wordpress_get_cron_schedules or wordpress_run_cron.

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