deletePoeSchedule

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

No annotations are present, so the description carries the burden of behavioral disclosure. It does add a useful authentication requirement, OMADA_WEB_USERNAME/OMADA_WEB_PASSWORD. However, for a destructive operation it does not explicitly state that deletion is permanent or describe any side effects on the schedule's associated ports or site.

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 compact: one sentence states the operation and target, and the second adds the required credential context. There is no filler or redundant restatement of schema 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 mutation tool with no annotations, no output schema, and zero schema description coverage, the description is incomplete. It omits the meaning of siteId, does not explain what the response will look like, and provides no guidance on error cases or side effects, leaving an agent under-equipped to invoke it correctly.

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 compensate, but it only says 'by id' without explicitly mapping that to the scheduleId parameter. The siteId parameter is completely unexplained, leaving an agent without enough meaning to confidently populate the optional parameter.

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 uses a specific verb and resource — 'Delete a PoE schedule by id' — clearly distinguishing it from siblings like createPoeSchedule, updatePoeSchedule, and listPoeSchedules. The 'by id' qualifier also clarifies the operation is targeted at a single existing schedule.

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 intended use is implied by 'Delete a PoE schedule by id', but the description gives no explicit guidance about when to choose this tool over alternatives such as deleteRebootSchedule or the other PoE schedule operations. It does not state prerequisites beyond credentials or mention any exclusion cases.

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