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

readOnlyHint=true already declares the safety profile, so the description's main added value is the default date window and the underlying GET /2/annotations endpoint. It says nothing about pagination, result caps, or ordering, which for a range-query list tool would be genuinely useful extra context.

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 compact sentences: identity and scope first, default behavior second, API endpoint last. Every clause carries information and nothing is padded.

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 3-parameter list tool with no output schema, the description covers identity, contents, defaults, and endpoint. Only return-shape/pagination details are absent, which is a minor gap against annotations that already signal a safe read.

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 coverage is 100%, so start_date, end_date, and no_time_off are fully documented in the schema itself. The description's range default largely restates the schema defaults and adds no format or filter semantics beyond them; baseline 3 applies.

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 enumerates what an annotation actually is — announcements, closed days, blackout dates — which is non-obvious domain vocabulary. No sibling covers annotations, so disambiguation is inherently satisfied.

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 default range ('today through one year out') tells the agent what happens if it omits arguments, but there is no explicit when-to-use/when-not guidance or reference to related tools such as wheniwork_list_time_off_requests for conflicting date information. Usage is only implied.

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