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

Goes well beyond the destructive/openWorld annotations: it discloses execution as the schedule's owner, the exit-code-0 gating of Do lines, the two-phase preview/proposal-id confirmation flow, and what the response contains (result, duration, log tail, or still-running). This is exactly the extra context the annotations cannot express.

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?

Front-loaded with the action, but the core content is crammed into one long run-on sentence with nested parentheticals ('its Run line: a node, python or bash script of the project, on Alcoven's servers'), which costs readability. The trailing 'For people who write in the schedule's folder' adds little.

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?

Given an output schema exists, the description covers the essential gaps: execution scope, permission model (acts as owner), the confirmation protocol, and the success/failure branching. Minor omissions like side-effect scope of Do lines or failure behavior are tolerable.

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%, so the baseline is 3, but the description adds real meaning about the 'proposal' parameter by explaining the confirm-then-rerun loop that makes a path-only call return a preview instead of a run. The path/project semantics are left entirely to the schema descriptions.

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 ('Runs a schedule or cron job on the project now') and immediately scopes it to execution of the schedule's script, not editing it. No sibling tool overlaps with this action, and the description makes the trigger semantics ('whatever its timetable') unambiguous.

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?

Gives concrete use cases ('to try a script or see its result') and describes the human-in-the-loop path for when confirmation is required. It stops short of naming when NOT to use it or pointing at any alternative tool, but the intent is clear.

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