Trigger cron job run

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

Annotations already indicate mutation and non-idempotency, but the description adds the key behavioral side effect of canceling active runs, which is not obvious from annotations alone. It also clarifies that the schedule itself is unchanged, providing useful context beyond the structured metadata.

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 four sentences, each earning its place. It front-loads the action and side effect, then adds the API endpoint, usage context, parameter clarification, and alternative tool reference without unnecessary fluff.

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 single-parameter tool with no output schema, the description covers the essential context: what the tool does, the side effect of canceling active runs, how to obtain the parameter, and a clear distinction from schedule-changing operations. It is complete enough for an agent to invoke correctly.

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 schema only describes cronJobId as 'The ID of the cron job.' The description adds crucial meaning: it identifies the ID as the cron job service's own id (srv-… or crn-… on older workspaces) and directs users to resolve it with render_find_service, significantly enhancing understanding beyond the 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?

Description clearly states 'Trigger a run for a cron job and cancel any active runs' with a specific verb and resource. It includes the exact API endpoint, and the mention of canceling active runs distinguishes it from the sibling render_cancel_cron_job_run.

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?

Explicit usage guidance: 'Triggers an immediate, out-of-schedule run' tells when to use it, and 'This does not change the schedule; use render_update_service for that' points to an alternative. Also advises resolving cronJobId with render_find_service, providing clear prerequisites.

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