listPoeSchedules

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

With no annotations, the description must carry behavioral disclosure. It does include the authentication requirement (OMADA_WEB_USERNAME/OMADA_WEB_PASSWORD) and explains what PoE schedules are conceptually, which is useful. However, it never explicitly states that the list operation itself is read-only and has no side effects, nor does it describe output or pagination behavior. This is adequate but has clear gaps.

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 concise and front-loaded with the action. Both sentences earn their place: the first states the purpose and scope, and the second explains the domain effect and required credentials. There is no filler or repetition.

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?

This is a simple one-parameter tool, and the description gives enough for a basic understanding: what it lists, at what scope, and what credentials are needed. However, there is no output schema, and the description does not clarify what the returned list contains, whether the call is safe/read-only, or where siteId comes from. It is reasonably complete for a simple tool but still leaves important gaps.

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 for the siteId parameter. The phrase 'for a site' loosely maps to siteId, but there is no explanation of how to specify or obtain the site ID, whether it is required, or how it relates to listSites. The single parameter is only minimally illuminated.

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 a specific action and resource: 'List PoE schedules for a site.' It adds helpful domain context about what PoE schedules do, which also distinguishes this from generic schedule tools. It does not explicitly contrast it with siblings like listRebootSchedules, so it stops short of a 5.

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 tool is used to retrieve PoE schedules for a specific site and notes that credentials are required. It does not explicitly state when to prefer this over related tools such as listRebootSchedules or how to obtain siteId. Usage context is present but exclusionary or alternative guidance is missing.

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