bb_upcoming

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

No annotations are provided, so the description carries the full behavioral burden. It does not state that the call is read-only, whether a prior bb_login session is required, whether overdue/past items are excluded, or how results are ordered or returned, leaving meaningful gaps for an unannotated 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?

A single compact sentence with the scope ('next `days` days') front-loaded and no filler. Every clause (content types, time window) earns 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?

For a listing tool with one optional parameter, no output schema, and no annotations, the description should at minimum cover the login prerequisite (bb_login is a sibling) and what the returned items look like. Neither is addressed.

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% and the single `days` parameter has no schema description, but the prose does define it as a forward-looking window ('for the next `days` days'), which adds real meaning. It still omits the default of 21 and the accepted range or edge cases, so it only partially compensates.

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 resource (Blackboard due dates) and enumerates the content types it returns (assignments, quizzes, Turnitin), so an agent can distinguish it from bb_announcements or bb_courses. It never explicitly contrasts itself with those siblings, but the intent is unambiguous from the text alone.

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 a forward-looking time window ('next `days` days') but gives no when-to-use guidance, no prerequisites, and never names an alternative tool for other date ranges or overdue items. Usage must be inferred entirely from the name.

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