Version

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered by structured data. In exchange, the description adds the return payload shape (version, job-set ID, job count), which is genuinely useful since no output schema exists. It stops short of describing format or cost, so a middle score fits.

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?

A single front-loaded sentence with zero filler, exactly proportionate to a zero-argument informational tool. Nothing repeats the name or restates annotations.

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 trivial read-only tool whose annotations cover safety and which requires no inputs, the description supplies the one thing missing elsewhere: what the call returns. Minor ambiguity remains around what a "job-set ID" identifies, but nothing needed to invoke it correctly is absent.

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 there is nothing for the description to disambiguate; baseline 4 applies. The sentence correctly implies no input is needed to retrieve the listed values.

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?

A specific verb ("Show") paired with three concrete resources (server version, job-set ID, job count) makes the purpose immediately legible. It implicitly differs from siblings like cron_get_status or cron_get_cluster by naming exactly what it returns, though it doesn't explicitly contrast with them.

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 offers no when-to-use guidance: nothing says whether this is a health check, a prerequisite for other calls, or how it differs from cron_get_status when an agent wants server state. The agent must infer its role from the return fields alone.

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