appcrane_run_cron_now

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

Despite no annotations, the description thoroughly discloses behavior: idempotent (skips if already running), runs docker exec, updates metadata, and returns exit code and log. Authorization implied ('App-admin or owner').

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?

Fairly concise, front-loaded with main purpose, and efficiently covers use cases and behavior in a few sentences. Could be slightly shorter, but nearly ideal.

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?

No output schema exists, but the description explains returns (exit code and log tail). Covers authorization, idempotency, and internal mechanism (docker exec). Complete for a single-action tool.

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 description adds no information about input parameters beyond what the schema already provides. The schema has 67% coverage (two of three parameters described), and the slug parameter lacks a description in both schema and description.

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 the tool triggers a cron job immediately, with concrete use cases and a clear verb + resource. It distinguishes itself from sibling tools like appcrane_list_cron.

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?

Provides explicit use cases ('test daily rebuild without waiting', 'rerun yesterday's failed job'). Does not explicitly compare to alternatives, but the intended context is clear.

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