zero_nightly

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

No annotations are present, so the description carries full burden. It mentions actions like regenerating Today.md and taking snapshots, but does not disclose whether these actions are destructive, require permissions, or have side effects (e.g., overwriting files, deleting queues). The 'cap 50' for fleeting queue implies a capacity constraint, but the behavioral impact is not fully explained.

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 line that front-loads the essential actions. It is concise, but could be slightly more structured (e.g., separating actions). Every component is listed, but no unnecessary text.

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 no output schema and no annotations, the description is minimally adequate. It lists actions but lacks details on expected outcomes, failure modes, or side effects. For a tool with no parameters, this is borderline acceptable but leaves room for improvement.

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 tool has no parameters, so the description does not need to explain parameter details. It adds value by outlining the actions performed without needing schema compensation. A baseline of 4 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 lists the actions performed: fleeting queue (cap 50), regenerate Today.md, health, and snapshot to a specific path. While it is in Thai, the overall purpose as a nightly maintenance cycle is evident, and it is distinguishable from sibling tools like zero_resolve or zero_init.

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?

No guidance is provided on when to use this tool versus other sibling tools. There is no mention of prerequisites, frequency, or conditions under which the nightly cycle should be triggered.

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