list_cron_jobs

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

No annotations provided. The description states 'list' which implies a read-only operation, but does not explicitly confirm no side effects or mention any permissions or limits. For a simple list tool, this is adequate.

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?

Single sentence that is front-loaded with the purpose and details. No redundant information; every word is necessary.

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 list tool with one optional parameter and no output schema, the description is sufficient. It covers what the tool lists and the main fields. Minor gap: does not mention behavior when no cron jobs exist, but not critical.

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 has one optional parameter 'server' with a clear description. Schema description coverage is 100%, so the baseline is 3. The tool description does not add meaning beyond the schema.

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?

Clearly states the action 'List' and resource 'scheduled cron jobs', and specifies the fields shown (schedule, command, user, active). Differentiates from sibling tools like create_cron_job and delete_cron_job.

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 implies usage when one wants to view cron jobs, but does not provide explicit guidance on when to use versus alternatives like edit or delete. No exclusions or context are given.

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