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

No annotations are provided, so the description carries the full burden for behavioral disclosure. The verb 'List' strongly implies a read-only operation with no side effects, which is transparent enough. However, the description does not explicitly state that it makes no modifications, nor does it mention any output format or pagination – acceptable for a list endpoint but not exhaustive.

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?

A single, well-structured sentence that front-loads the action and resource, then adds scope and examples. No fluff or redundancy; every clause earns its place.

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 simple tool with one optional parameter and no output schema, the description is complete. It covers what is returned, the time window, and concrete examples of service types. No critical information appears missing.

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 fully documents the 'days' parameter including its default. The description repeats the default and ties it to the 'due within' window, adding minimal extra meaning beyond the schema. Baseline 3 applies because the schema does the heavy lifting.

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'), resource ('services and permits'), and scope ('due within the next N days'), with concrete examples (hood cleanings, suppression inspections, permit renewals). This clearly distinguishes it from the sibling 'list_overdue_services' (which implies past due rather than upcoming).

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?

Provides a clear context of what the tool returns (upcoming services/permits), but does not explicitly state when to use it versus alternatives like list_overdue_services or search_services. The differentiation is implied by the 'due within the next N days' wording, but no direct routing guidance is offered.

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