Schedule load

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

Annotations already establish that this is a safe, read-only, idempotent operation. The description adds useful behavioral detail beyond annotations: the default 24-hour window, maximum 168 hours, timezone default, and the fact that results are grouped by hour and minute with gap detection.

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?

Two dense sentences with no wasted language. The core operation, defaults, limits, grouping, and gap detection are all front-loaded efficiently.

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?

With only two optional parameters, rich annotations, and no output schema, the description is nearly complete. It explains the time window, timezone behavior, and the conceptual shape of the result (hour/minute grouping plus gap detection), though it does not describe the exact return structure in detail.

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 carry parameter meaning. It explains that hours defaults to 24 and maxes at 168, and that tz defaults to UTC, which meaningfully compensates for the bare schema. It could still specify timezone format or minimum hours, but both parameters are substantially clarified.

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 states a specific analysis operation: upcoming runs for enabled schedules grouped by hour/minute, including overlapping jobs and empty minute positions. It is clear what resource is being analyzed and what insight is produced, though it does not explicitly differentiate itself from siblings like cron_schedule_duplicates or cron_suggest_slot.

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?

Usage is implied by the concept of schedule pressure and load inspection, but the description never says when to prefer this tool over cron_schedule_duplicates, cron_suggest_slot, or cron_get_job_trends. No exclusions or prerequisites are provided.

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