List cronjobs

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

Without annotations, the description bears full responsibility for disclosing behavior. It only says 'List cronjobs', omitting details like return format, pagination, permissions, or side effects (none expected). This is insufficient for an agent to understand the tool's behavior.

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 very short (one sentence) with slight redundancy. It is not overly verbose, but it could be more concise while adding value. The calibrations show that a score of 3 is suitable for a minimal but not wasted description.

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 parameters, no output schema, and no annotations, the description should at least clarify what output the tool returns (e.g., list of cronjob identifiers). It lacks this context, leaving the agent underinformed for a simple listing 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?

There are no parameters, so the schema is empty and fully covered. The description adds no parameter-specific information beyond the schema, but no params means minimal burden. Baseline score of 3 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 states 'List cronjobs' which clearly indicates the action and resource. The parenthetical 'get_cronjobs' adds slight redundancy but does not detract. The tool's name and sibling tools (e.g., cronjob_add, cronjob_delete) make its listing intent clear.

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 alternatives (e.g., when to list cronjobs vs. add/delete). The description does not indicate prerequisites, context, or exclusions.

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