list_cronjobs

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

With no annotations, the description carries the full behavioral burden. It implies read-only behavior through the verb 'List' and lists the output fields, but it does not explicitly confirm no side effects, mention auth/permissions, or discuss pagination/batching behavior. Basic for a list tool but not fully transparent.

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 tight and efficient: one purpose sentence followed by a short parameter list. No filler, no repetition of schema defaults, and the core action is front-loaded.

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 an output schema exists and the operation is a straightforward list, the description covers all parameters and the returned columns. It does not mention errors, permissions, or limits, but for a read-only list tool this is a minor gap rather than a blocking one.

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?

Schema description coverage is 0%, so the description must compensate. It adds real meaning: namespace empty means all namespaces, label_selector filters CronJobs, cluster empty means default. However, it does not specify the exact label selector syntax or value format, leaving some ambiguity.

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 first sentence states a specific verb and resource ('List CronJobs') and even enumerates the output columns (NAMESPACE, NAME, SCHEDULE, etc.). It is clearly distinct from sibling tools like list_jobs or create_job_from_cronjob.

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 parameter descriptions provide clear usage context: namespace defaults to all namespaces, label_selector filters results, and cluster targets which cluster. It does not explicitly name alternative tools or state when not to use this tool, but the read/list intent is obvious from the description.

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