k8s_get_cronjobs

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

With no annotations, the description must disclose behavioral traits. It mentions the listed fields and namespace behavior but does not state that it is a read-only operation or any prerequisites/permissions. It is accurate but lacks explicit safety/property disclosures.

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 sentence plus a concise instruction, no wasted words. It is front-loaded with the core purpose. Slightly under-specifies parameters, but conciseness is good.

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 the tool has 3 parameters with no schema descriptions and no output schema, the description is incomplete. It covers the output fields and namespace behavior but omits parameter usage for context and label_selector. Adequate but with clear gaps.

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 should explain parameters. However, it only implicitly addresses namespace via the 'Omit namespace' phrase, and does not explain 'context' or 'label_selector'. The description adds minimal semantic value 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?

The description clearly states the tool lists Kubernetes CronJobs and enumerates the returned fields (schedule, suspension status, active jobs, last schedule/success times). It distinguishes from sibling tools like k8s_get_jobs by specifying CronJobs specifically.

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 gives one usage tip ('Omit namespace for all namespaces') but does not provide when-to-use or when-not-to-use guidance relative to other list tools. No alternatives or exclusions are mentioned.

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