cron_explain

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

With no annotations, the description carries the full burden. It discloses the input scope (5-field) and the nature of the output ('plain English'), but does not mention validation behavior, error handling, or the exact output format. This is minimal but adequate for a simple read-only utility.

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, well-structured sentence that front-loads the verb and resource, with no unnecessary words. It perfectly balances brevity and informativeness.

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 single-parameter utility with no output schema, the description is complete: it explains what the tool does, what input it expects, and what the output looks like ('plain English'). No additional context is necessary.

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 schema already documents the 'expr' parameter with an example, and the description adds the field order ('minute hour day-of-month month day-of-week'), enriching the parameter's meaning beyond the schema. Since schema coverage is high, this extra context boosts the score above baseline.

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's function with a specific verb ('Explain') and resource ('5-field cron expression'), and it identifies the exact field order. This distinguishes it from any sibling tools, which are all unrelated utilities.

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 clearly implies when to use the tool: whenever a 5-field cron expression needs translation to plain English. It does not explicitly discuss alternatives or exclusions, but no sibling tool serves a similar purpose, so the context is clear.

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