list_cronjobs

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

No annotations are provided, so the description carries the full behavioral burden, yet it only implies a read-only operation via the word 'list'. It says nothing about pagination, ordering, permissions, or result scope for a server that may host many cronjobs.

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?

Two words are maximally efficient and front-loaded with no filler, but the size reflects under-specification rather than tight editing. It is concise without being informative.

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 no-parameter list tool this could be more complete by stating what is returned (or that all cronjobs are returned unconditionally). With no annotations and no output schema, the description leaves an agent guessing about scope and result shape.

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 takes zero parameters, so per the rubric the baseline is 4. There is nothing for the description to disambiguate at the parameter level.

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?

"List cronjobs" names a verb and resource, so an agent can guess the operation, but it is essentially a restatement of the tool name list_cronjobs and provides no additional information. It does not distinguish the tool from siblings create_cronjob or delete_cronjob beyond the self-evident 'list' prefix.

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?

There is no when-to-use guidance, no prerequisites, and no mention of alternatives such as create_cronjob or delete_cronjob. The purpose is inferable from the name, but the description itself supplies no routing guidance.

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