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

With no annotations, the description carries the full burden of behavioral disclosure. It states what is listed and the default window, but does not mention return format, pagination, sorting, or any side effects. As a read-only listing tool, this is acceptable but not rich in additional behavioral 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?

The description is a single, well-structured sentence that front-loads the core action and resource, includes relevant examples, and avoids unnecessary words. Every word 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?

The tool is a simple list operation with one optional parameter and no output schema. The description adequately conveys the scope and default behavior. It could be slightly more comprehensive by noting the return format or how it differs from 'overdue', but for a low-complexity tool it is generally complete.

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% and the single parameter 'days' already has a clear description including the default value. The tool description repeats the default and adds examples, but does not add significant semantic value beyond the structured 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?

The description uses a specific verb 'List' and clearly identifies the resource as 'services and permits due within the next N days', with examples (hood cleanings, suppression inspections, permit renewals). It distinguishes from sibling tools like list_overdue_services by the time window, making 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 implies usage for looking ahead at upcoming services due, and notes the default 30-day window. However, it provides no explicit guidance on when to prefer this over alternatives like list_overdue_services or search_services, nor does it state any exclusions or prerequisites.

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