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

The description adds useful behavioral context by stating that the report is computed from stored next-due dates against today at call time, meaning results are live and time-sensitive. It also flags that this is a Pro feature, which is an access/entitlement consideration. Since the annotations do not mark the tool as read-only, the description's implicit report-only framing is helpful but not explicit about whether invoking it has side effects.

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 compact and front-loaded: the first sentence delivers the full scope and categories, and the second provides computation semantics and the Pro-feature caveat. Every sentence earns its place with no 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 tool with one optional parameter and no output schema, the description does a solid job of explaining the output categories and the time-based nature of the report. It stops short of describing the exact output shape, sorting, or whether the result includes asset identifiers, but the core calling context is adequately covered.

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?

The schema already fully documents within_days with a description and bounds, so the baseline is 3. The tool description repeats the default of 30 days but adds no additional meaning beyond what the parameter description already provides.

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 names a specific deliverable — the due report across every asset — and enumerates exactly what it covers: overdue items, days overdue, upcoming items within N days, later items, and items with no schedule. It does not explicitly contrast itself with maintenance_export or maintenance_log, so it earns a 4 rather than a 5.

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 this is the tool to use when a consolidated due/overdue report is needed, and it notes the global scope across every asset. However, it gives no explicit guidance about when to use this tool instead of maintenance_export, maintenance_log, or asset_history, nor does it mention any exclusions or prerequisites beyond the Pro feature note.

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