get_overdue

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

No annotations are provided, so the description carries the burden; the verb 'Return' does signal a non-destructive read, which is the main behavioral fact an agent needs here. It says nothing about what counts as an item, ordering, empty results, or whether the scope respects enrollment, all of which would have to be discovered empirically.

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?

A single front-loaded sentence with zero filler and the scope constraint placed after the core action. It is efficient, though the brevity is a symptom of under-specification rather than deliberate precision.

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 no parameters, no annotations, and no output schema, the description is the only documentation, and 'Ufora items' is vague about whether assignments, quizzes, and discussions all appear. For a low-complexity zero-argument listing tool this is minimally adequate, but the item taxonomy and default scope are left undefined.

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 tool takes zero parameters, so there is no parameter surface for the description to explain and the baseline of 4 applies. The description appropriately restricts itself to defining the implicit scope (current courses) rather than inventing parameter detail.

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 ('Return') plus a clearly scoped resource ('overdue Ufora items across current courses'), which is enough to separate it from the name-adjacent sibling get_upcoming_due by implication. It stops short of explicitly naming that sibling, so an agent must infer the overdue-vs-upcoming split rather than being told.

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 only usage signal is the embedded scope qualifier 'current courses,' which implicitly excludes past/archived courses. There is no when-to-use statement, no prerequisite, and no named alternative (e.g., get_upcoming_due for future deadlines), even though the sibling list contains an obvious counterpart.

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