cron_list

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

With no annotations, the description carries the burden. The verb 'List' clearly indicates a read-only operation with no side effects, which is transparent. However, it does not mention whether it returns a specific format or whether it covers all users' crontabs, but for a simple list tool this is adequately disclosed.

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, concise sentence that is front-loaded with the action ('List') and includes the necessary context ('current crontab entries on the router'). No wasted words; every part contributes meaning.

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 zero-parameter list tool with no output schema, the description is essentially complete. It states the exact action and scope. A slight gap is that it does not specify whether it lists all crontabs or just the current user's, but this is a minor omission for such a simple 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 tool has zero parameters, so the input schema is fully covered and there is no need for additional parameter explanations. The baseline of 4 applies for a parameterless tool.

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 uses the verb 'List' with a specific resource 'crontab entries on the router,' making the tool's purpose unambiguous. It distinguishes itself from all sibling tools, as no other tool mentions cron or crontab.

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 context is clear: this tool is used to view current crontab entries on the router. There are no alternative tools for this task among the siblings, so explicit exclusion is not necessary. The description gives enough context for an agent to choose this tool when listing cron jobs.

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