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

Annotations already cover the safety profile (destructive, non-idempotent, open-world), and the description adds genuinely new behavioral facts: it returns only that Croncool invoked the job rather than the target's response, each call re-sends the configured request, and repeated calls re-fire with downstream write/message/billing effects.

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?

Three tightly packed sentences with the trigger condition front-loaded, then the return-value caveat, then the repeat-call hazard. Every sentence carries distinct information and none is wasted.

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?

An output schema exists so return structure need not be explained, yet the description still flags the key caveat that the response only confirms invocation. Combined with the re-send hazard, an agent has everything needed to call this safely.

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% with a single well-formed jobId (uuid) parameter, so the schema already does the work. The description adds no syntax or format detail beyond what is documented, making the baseline 3 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?

States a specific verb and resource ('run or trigger a cron job now') and makes the scope unambiguous. An agent can distinguish it from get_job_runs or get_workflow_run without opening a schema.

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?

Opens with the triggering condition ('when someone asks to run or trigger a cron job now') and explicitly excludes a nearby use case ('Not for checking a run's result'), routing the agent toward the read-side siblings.

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