List CronJobs

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

The description states 'Read-only', which is a key behavioral trait. Without annotations, the description carries the burden of disclosure, but it does not mention potential side effects, permission requirements, error behavior, or performance characteristics. For a simple read-only list tool, this is adequate but not rich.

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 consists of two concise, front-loaded sentences. The first sentence states the purpose and return fields, the second provides usage guidance and a behavioral note. No unnecessary words, every sentence adds value.

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 sufficiently explains the return values (schedule, suspend status, etc.) and usage. It covers the essential context needed for selection and invocation, including read-only behavior and namespace handling.

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 already describes the namespace parameter with 'omit for all namespaces'. The description repeats this, adding no new semantic information. Since schema_description_coverage is 100%, the baseline is 3.

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 verb 'List', the resource 'CronJobs', and specifies the fields returned (schedule, suspend status, active job count, last schedule time). This adequately distinguishes the tool from sibling list tools like list_jobs or list_deployments.

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 explicitly says 'Omit namespace for all namespaces', providing clear guidance on when to include or omit the namespace parameter. However, it does not explicitly state alternatives or when not to use this tool, which would be helpful given many sibling list tools.

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