List upcoming (skippable) services

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

Annotations already provide readOnlyHint, openWorldHint, and idempotentHint, reducing the burden on the description. The description adds useful behavioral context: output includes both scheduled and already-skipped services, and it pulls from the service calendar. It also repeats 'Read-only' reinforcing safety, though it doesn't discuss pagination or ordering—acceptable for a simple list tool.

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 sentences, front-loaded with the verb and resource, no wasted words. The first sentence describes scope and output; the second gives clear usage guidance. Perfectly sized for the tool's simplicity.

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 no parameters, no output schema, and helpful annotations, the description fully covers purpose, return content, and alternative tools. It is complete for an agent to select and invoke correctly, with no significant 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?

With zero parameters, the schema has no properties to explain, so baseline 4 applies. The description does not need to add parameter details and correctly focuses on output semantics instead.

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 lists upcoming scheduled collection days from the service calendar, specifying the output includes skip identifiers (rid, clid), service date, and skip status. This distinguishes it from siblings like list_service_history (past services) and skip_service (mutation). The verb 'List' and specific resource 'upcoming services' make the purpose unambiguous.

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 explicitly directs users to use crowntown_skip_service for skipping/unskipping, establishing a clear alternative and when this read-only tool is appropriate. It also implies use when needing identifiers to skip, giving practical guidance beyond basic purpose.

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