get_release_calendar

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

Annotations already declare readOnlyHint and destructiveHint, but the description adds valuable algorithmic detail: it scans only release/RC-titled tickets, orders in-flight releases, computes cadence based on lookback, and flags parked queues. This transparency goes beyond the basic safety profile and explains the tool's logic without contradiction.

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 front-loaded with a concise summary, then expands into a well-organized bulleted breakdown. Each sentence adds unique information, including the conditional ETA calculation and the parked-queue flag threshold. No redundancy or empty phrasing.

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's complexity and the presence of an output schema, the description is complete. It covers scope, per-project behavior, computational method, and parameter meaning. An agent can confidently invoke it with defaults or custom parameters, and the output schema handles return-value details.

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 has no descriptions (0% coverage), so the description carries full responsibility. It explains each parameter clearly: projects as comma-separated keys with blank meaning all, lookback_days as the shipped-release window with default 30, and instance as optional. This is comprehensive semantic guidance.

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 it scans release/RC-titled tickets across projects and reports in-flight releases, recent ships, cadence, and ETAs. It provides a specific scope and features that distinguish it from sibling reporting tools. The first line summarizes the resource and output.

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 implies usage for release tracking but does not explicitly state when to use it over alternatives like get_roadmap or get_team_dashboard. There is no when-not-to-use or alternative guidance, leaving the choice to inference rather than direct instruction.

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