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

Annotations only supply destructiveHint=true, so the description usefully adds that this modifies live status-page data and can notify subscribers — an important side effect an agent should anticipate. It also maps the call to the underlying POST endpoint and states the return. It stops short of mentioning auth/permission requirements or whether a scheduled maintenance can be canceled after creation.

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 tight sentences: capability and side effect first, then parameters, endpoint, and return value. Every clause carries information and nothing is padded.

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 10-parameter mutation tool with only destructiveHint covered by annotations and no output schema, the description supplies the effect on live data, notification behavior, and the return shape. It omits permissions and post-creation mutability, but what an agent needs to invoke it correctly is largely present.

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%, so every parameter is already documented, including the per-component 'statuses' impact mapping and enum values. The description enumerates the same fields (name required, message, components, statuses, status, start/end, duration, notify) without adding syntax, defaults, or interaction rules beyond the schema. 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?

States a specific verb+resource ('CREATES a new scheduled maintenance') and immediately characterizes the scope of the effect on live status-page data. The resource name itself separates it from instatus_create_incident, so an agent can select correctly without opening schemas.

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?

The description implies the usage context (scheduling maintenance that affects live status-page data and notifies subscribers), which is useful framing. But it never states when to prefer this over instatus_create_incident, instatus_update_maintenance, or what prerequisites (page_id ownership, permissions) must hold. Usage is inferable rather than explicit.

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