status_page_maintenance

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

Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the bar is lower. The description adds the genuinely useful non-annotated fact that no credentials are required, but says nothing about return shape, pagination, or window fields.

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?

Two short sentences, resource scope front-loaded and the auth note appended. Nothing redundant; every sentence 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?

For a simple read-only tool with full annotation coverage and one well-documented parameter, the description is nearly complete, and 'scheduled and ongoing' hints at the returned content. It stops short of noting pagination or whether historical windows are included, which matters slightly given no output 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?

There is a single parameter (slug) with 100% schema description coverage, so the schema carries the full burden. The description adds no format hints beyond the schema's pattern and address-derived explanation; 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 specific resource (scheduled and ongoing maintenance windows) and scopes it to a public status page, which distinguishes it from the workspace-level sibling list_maintenance. However, it omits an explicit verb, so the agent must infer that it retrieves/lists rather than manages these windows.

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?

'No credentials needed' gives an implied usage condition (public status page, no auth), but there is no statement of when to prefer this over list_maintenance or status_page_overview/status_page_incidents. Usage is inferable from the suffix pattern of the sibling tools but not stated.

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