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

readOnlyHint=true already signals a safe read, and the description adds genuine context on top: the default window (start of today through one year out) and the semantic meaning of the annotation types, including that blackout days block time off. It does not cover pagination, max result size, or auth requirements, which keeps it short of a 5.

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 tight sentences plus an endpoint reference; the resource definition and its default window are both front-loaded with zero filler.

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 read-only list tool with no output schema, the description tells the agent what entities come back, their meaning, and the default range, so it is nearly self-sufficient. It omits pagination/volume expectations and any auth or rate-limit note, which are the only remaining gaps.

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 100%, so the schema already documents date formats and the no_time_off flag; baseline is 3. The description's 'today through one year out' reinforces the default range for start_date/end_date and its mention of time-off blocking loosely maps to no_time_off, but adds no format or syntax detail beyond the schema.

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?

States a specific verb (List) and resource (schedule annotations), then unpacks what that resource contains: announcements, business-closed days, and blackout dates. No sibling tool covers this resource, so an agent can route to it unambiguously without opening a schema.

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 supplies a useful behavioral default ('today through one year out') but never states when to reach for this tool versus siblings like list_time_off_requests or get_shift, nor any exclusion. Usage is only implied by the resource being listed.

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