uplus_list_homeworks

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

No annotations are supplied, so the description carries the full disclosure burden. It valuably explains that refresh_page_state opens each answer page because REST status can lag the real submit button, which hints at cost and reconciliation behavior — but it omits whether the tool mutates anything, whether auth is required, and roughly how expensive the refresh is per course.

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 short sentences, the primary behavior front-loaded and the parameter caveat second. The awkward line breaks are cosmetic; no sentence is filler.

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?

An output schema exists, so return shape needn't be described. Both optional parameters are addressed and the lag/reconciliation nuance is covered, leaving nothing an agent needs in order to call 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 coverage is 0%, so the description must compensate, and it does: it explains that an omitted course_id means all courses, and describes refresh_page_state's purpose (read the real submit button off each answer page) rather than just restating the name. It lacks format detail for course_id, but the core semantics are conveyed.

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 first sentence gives a specific verb and resource ('List homework status') plus the scope rule ('one course, or all courses when omitted'). It separates this from the sibling uplus_inspect_homework only implicitly, by implying this is a bulk status listing rather than a deep single-item inspection.

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?

'or all courses when omitted' and the refresh_page_state aside give clear invocation conditions for both modes. However, the description never states when an agent should prefer uplus_inspect_homework or uplus_answer_homework instead of this list, and no prerequisites (e.g. login) are mentioned.

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