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

The annotations declare readOnlyHint=true and destructiveHint=false, but the description says the user can 'record authorized observations interactively,' which implies a write operation. This contradicts the read-only annotation, so the description fails to accurately disclose behavior.

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 short and front-loads the use case, then states what loads and adds a risk disclaimer. The contradictory 'record observations' clause is the main flaw, but the overall size is appropriate.

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 an 8-parameter tool with no output schema, the description is incomplete: it does not map filters to parameters and contradicts the read-only annotation. An agent would lack enough detail to invoke it correctly without inspecting the schema.

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 has 8 parameters with 0% description coverage, so the description must compensate. It only says 'with filters and pagination,' which hints that filters exist but does not explain any specific parameter (e.g., overdueOnly, criticalOnly, assetId, from/until).

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 states a specific verb and resource: 'Loads upcoming/overdue authorized schedules with filters and pagination.' This clearly conveys that the tool retrieves schedules, but it does not explicitly differentiate from the sibling list_due_maintenance.

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?

It provides a clear when-to-use context: 'Use this when the user wants to browse due schedules, focus on overdue work or record authorized observations interactively.' However, it does not state when not to use it or name alternatives.

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