add_cron_entry

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

No annotations are provided, so the description carries the full burden. It mentions 'current user's crontab', which scopes the operation, but does not disclose side effects such as whether the entry is appended, whether duplicates are allowed, or whether the schedule is validated. The description is too minimal to provide adequate behavioral transparency for a mutation tool.

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?

A single, front-loaded sentence that fully states the tool's purpose and scope with no wasted words. It earns its place and is immediately scannable.

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 simple 2-parameter tool with an output schema present, the description is adequate but sparse. It omits any mention of validation behavior or duplicate handling, but the schema and output schema likely fill some gaps. Overall it is minimally complete for the tool's simplicity, though richer context would be better.

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 input schema already provides complete descriptions for both parameters (command and schedule) with 100% coverage. The tool description itself adds no parameter-specific meaning, so it rests at the baseline for high schema coverage.

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 uses a specific verb ('Add') and resource ('a new entry to the current user's crontab'), clearly distinguishing it from siblings like 'list_crontab', 'remove_cron_entry', and 'validate_cron_expression'. It unambiguously states the tool's function.

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?

The description clearly implies the intended use: when you want to create a new cron job. It does not explicitly exclude alternatives or mention 'when not to use', but the sibling set makes the context obvious, and there are no competing 'add' tools. This meets the 'clear context, no exclusions' level.

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