deleteRebootSchedule

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

No annotations are provided, so the description carries the behavioral disclosure burden. It does add an authentication prerequisite (OMADA_WEB_USERNAME/OMADA_WEB_PASSWORD) that is not inferable from the schema. However, it does not mention side effects, irreversibility, or failure behavior, leaving notable behavioral gaps for a destructive operation.

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?

The description is two short sentences with the primary action front-loaded and no redundant wording. Every sentence contributes meaningful information.

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 destructive tool with no annotations and no output schema, the description is insufficiently complete. It omits siteId semantics, expected response or errors, and edge-case behavior. An agent can proceed only if scheduleId alone is always sufficient and the auth variables are known externally.

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 0%, so the description should explain both parameters. It only says 'by id', which adds little beyond the scheduleId parameter name. The optional siteId parameter is entirely unexplained, leaving an agent without enough context for correct invocation.

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 clearly states the action (delete), the resource (reboot schedule), and the selection mechanism (by id). This distinguishes it from sibling tools such as createRebootSchedule, updateRebootSchedule, and listRebootSchedules.

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 does not provide explicit when-to-use or when-not-to-use guidance, nor does it point to alternatives. The credential requirement is a prerequisite, not usage guidance, so an agent must infer suitability from the tool name and action alone.

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