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

Annotations already declare readOnlyHint=true, openWorldHint=true and destructiveHint=false, so the safety profile is covered. The description adds the concrete data shape (checks disabled, cron, duration, run history) and the underlying endpoint, but says nothing about pagination, result volume, or auth/subaccount scoping 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?

A single compact sentence front-loads the resource and its contents, followed by the endpoint. Nothing is padded, though the 'GET /maintenance.' fragment is close to redundant with the tool name.

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 low-complexity read-only list tool with a fully documented single parameter and annotations covering safety, this is nearly sufficient. It still omits any mention of the customer_id scoping parameter or how the result differs from nodeping_get_maintenance, which an agent calling an MSP-aware endpoint would benefit from knowing.

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% and the single optional customer_id parameter is fully documented in the schema, including its MSP/omit-for-own-account semantics. The description adds nothing about parameters, so the baseline 3 applies.

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 names the resource (maintenance entries) and enumerates the salient contents (disabled checks, cron, duration, next/last runs), which is more specific than the title alone. It does not, however, explicitly distinguish this list operation from the sibling nodeping_get_maintenance, so an agent must infer the difference.

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?

There is no statement of when to use this versus nodeping_get_maintenance (single entry) or nodeping_list_schedules, and no prerequisites or exclusions are given. The GET endpoint hint implies a read but offers no routing guidance.

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