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

Adds substantial context beyond the annotations: public visibility to visitors, subscriber notification gating on the four notify flags (all default off), the effect of automation=true, and the return value (maintenance id). The 'WRITE' framing is consistent with readOnlyHint=false and destructiveHint=true, so there is no contradiction.

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?

Four tight sentences with the write scope front-loaded, followed by visibility, notification gating, automation, and return value. No filler and every sentence carries an operational fact.

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 15-parameter mutation tool with no output schema, the description covers the key unknowns: what becomes publicly visible, when subscribers are contacted, how automation governs lifecycle, and what the call returns. Remaining details are fully covered by the schema and annotations.

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%, so the baseline is 3; the description still adds meaning by emphasizing that subscribers are only told when a notify switch is enabled and that all notify flags default off, plus clarifying the self-managing behavior of automation. It does not add format details for start/end, which the schema already covers.

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 and resource ('WRITE: schedule a planned maintenance on the PUBLIC status page') and names the endpoint POST /maintenance/schedule. This cleanly separates it from start_maintenance, finish_maintenance, and update_maintenance among its siblings.

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?

Gives clear context: it is for planned/upcoming maintenance, visible publicly, with subscriber notification only via explicit notify flags. It does not explicitly say when to prefer start_maintenance or finish_maintenance instead, so the routing to alternatives is implied rather than stated.

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