admin_run_cron_job

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

With no annotations, the description must carry the behavioral burden. It only states 'Run a cron task' and 'requires admin privileges', offering no insight into effects, idempotency, or potential side effects. The agent gains little beyond the tool name.

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, short sentence of 8 words that immediately conveys the core purpose and a key constraint. Every word earns its place.

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 tool with one parameter and no output schema, the description is mostly complete. It covers the action, resource, and access level. It lacks details on return values or asynchronous behavior, but these are minimally critical for a trigger action.

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 input schema already provides a description for the 'task' parameter, achieving 100% coverage. The tool description adds no new semantic value; it merely paraphrases the parameter's purpose. Baseline 3 is appropriate.

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 clearly states 'Run a cron task by name' with the specific resource (cron task) and action (run). It also notes the admin privilege requirement, setting it apart from other tools like admin_list_cron_jobs.

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 explicitly states that admin privileges are required, giving clear context for when this tool is appropriate. However, it does not mention when not to use it or compare it to alternatives like admin_list_cron_jobs, but the sibling list provides natural differentiation.

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