Get upcoming Blackboard work

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

Goes well beyond the readOnlyHint annotation: it discloses sort order, the window boundary ('end of the last day, Syracuse time'), inclusion of recently overdue unhanded-in work, and an interpretation rule for the 'unknown' status ('never treat unknown as missing work'). That last point materially changes how an agent should reason about the results.

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?

Front-loaded with the core purpose, and the routing statement follows immediately. The trailing 'Read-only' repeats the readOnlyHint annotation and is the one sentence that does not fully earn 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?

With no output schema, the description carries the burden of explaining returns, and it does: due-date ordering, submission status, and the full status vocabulary with edge-case handling. Minor omissions remain (result size limits or pagination), but an agent has what it needs to call and interpret this 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?

The single 'days' parameter is fully described in the schema, so the baseline is 3. The description adds genuine meaning by specifying that the window terminates at the end of the last day in Syracuse time, which clarifies how the integer is actually interpreted.

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 and resource plus scope: 'Upcoming assignments and assessments across ALL Blackboard courses, sorted by due date, with submission status.' The ALL-courses scope and the 'what do I have due?' framing distinguish it from course-scoped siblings like get_assignments and get_course_content.

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 positions itself as 'the one call to answer "what do I have due?"', which is clear routing guidance. It also notes it recovers recent unsubmitted items from the past few days. It does not name an alternative tool or state when NOT to use it, so it falls short of a 5.

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