list_public_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, so the safety profile is covered; the description still adds real context: no credentials are needed, public window records come back, and a missing page or one with MCP access disabled yields an error. It stops short of describing ordering or volume of returned windows, so it is strong rather than exhaustive.

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?

Three sentences, each carrying distinct information: what it reads, when to use it versus the sibling, and what comes back including failure modes. The identifying scope (public, no credentials) is front-loaded with zero 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 single-parameter read tool with full annotation coverage and no output schema, the description supplies everything needed: auth posture, sibling routing, and error conditions. There is no gap an agent would need to guess at before calling it.

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% and the slug parameter already documents its format and the /status/<slug> address convention, so the schema does the heavy lifting. The description only restates that a published status-page slug is required, adding no new syntax or constraint detail.

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 a specific verb and resource (read scheduled and ongoing maintenance windows) and pins the scope precisely: public, per-status-page, unauthenticated. It explicitly distinguishes itself from list_maintenance, so an agent can separate the two without inspecting either schema.

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 states the use case ('explain announced downtime') and names the alternative for the other case ('authenticated list_maintenance is the project-wide management view'), which is an explicit when-to-use/when-to-use-something-else split. Nothing is left to inference.

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