remove_cron_entry

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

Without annotations, the description relies entirely on itself. It discloses a key behavior: 'Shows what will be removed,' indicating a preview or output. However, it does not state that removal is permanent/irreversible, or mention any permissions or side effects. The destructive nature is implied by the verb 'Remove' but not elaborated.

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 extremely concise—two short sentences. It front-loads the purpose and adds one behavioral detail. No waste.

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 the tool's simplicity (one parameter) and the presence of an output schema, the description is adequate but not rich. It explains the removal action and shows behavior, but lacks a cautionary note about permanence or a connection to sibling tools. The 'Shows what will be removed' could be misinterpreted as a dry-run, so a bit more context would help.

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 fully describes the 'pattern' parameter ('Text pattern to match the entry to remove'), achieving 100% coverage. The description adds no additional semantics beyond that, so it meets the baseline of 3.

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's purpose: 'Remove crontab entries matching a pattern.' This is a specific verb (Remove) with a resource (crontab entries) and a matching mechanism. It also adds a distinguishing behavior ('Shows what will be removed') that separates it from list/search tools.

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 explicit guidance on when to use this tool versus alternatives like search_crontab or list_crontab. The description implies it is for removal but does not provide context on when to prefer it, prerequisites, or when not to use it. For example, it doesn't suggest using search_crontab first to preview matches.

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