get_homework

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

No annotations are provided, so the description carries the full burden. It conveys that this is a read of pending assignments and lists the return fields, but says nothing about auth requirements, whether completed homework is excluded, or how the window interacts with the pending filter. Adequate but thin for an annotation-free tool.

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?

Short and front-loaded: the one-line purpose leads, followed by return fields and the argument note. The 'Args:' block is slightly verbose for a single optional parameter but wastes little space.

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?

With an output schema present, return values need not be re-explained, and the sole optional parameter is documented. The only remaining gap is the absence of any safety/permission context for an annotation-free tool, which is minor for a read-only fetch.

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 must compensate for the single parameter, and it does: days_ahead is explained as 'Number of days to look ahead (default: 14)'. It adds real meaning beyond the bare integer schema, though it doesn't clarify whether the window filters the pending set or the due-date range.

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 a specific verb (fetch) and resource (pending homework assignments) and enumerates the returned fields, so the agent knows exactly what it retrieves. It does not, however, distinguish itself from the many sibling read tools (get_exams, get_timetable, get_today), 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?

There is no when-to-use guidance, no prerequisites, and no mention of alternatives among the siblings. The word 'pending' hints at scope but the description never says when this tool is the right choice versus get_exams or get_timetable.

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