createPoeSchedule

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

With no annotations, the description carries the full behavioral burden and does so well. It discloses the destructive side effect (hard PoE power cut, collateral port drops, including PoE-powered controllers) and the authentication requirement, which are exactly the non-obvious traits an agent needs.

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 efficient sentences front-load the purpose, then add the high-value safety warning and credential requirement. No filler, no repetition, and 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 mutating creation tool with no annotations, no output schema, and a nested free-form data object, the description leaves critical gaps: it never mentions siteId, does not specify what fields data should contain beyond a time-range-to-port binding, and says nothing about response behavior. An agent would still have to guess at the request shape.

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?

The data parameter gains meaning beyond the schema: it binds a time-range profile to switch ports and points to listTimeRanges. However, siteId is completely undocumented in both schema and description, and data's additionalProperties are unconstrained, so parameter semantics are only partially enriched.

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 the action 'Create' and object 'PoE schedule' clearly and immediately. It also distinguishes the tool from createRebootSchedule by warning to prefer a reboot schedule on Omada-managed devices, and from update/delete/list siblings by the create verb.

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?

Explicitly tells the agent to prefer createRebootSchedule when the target is an Omada-managed device and explains why: PoE is a hard power cut and drops anything else sharing the port. It also names the required credentials, giving a clear precondition for calling the tool.

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