Get upcoming Blackboard work

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

Annotations already declare readOnlyHint=true, so the added 'Read-only' is redundant rather than informative. The description does add useful behavioral context: results are cross-course, limited to upcoming items, and sorted by due date. It stops short of describing pagination, response format, or whether assignment details are included.

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?

Three short sentences, front-loaded with scope and ordering, then a purpose statement. The only redundancy is 'Read-only', which duplicates annotations, but the overall length is appropriate and every sentence 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 simple read-only tool with one optional parameter, the description fully conveys the resource, the scope, the ordering, and the intended use case. The schema covers the parameter, and annotations cover safety. Nothing critical is missing.

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 sole parameter is fully documented in the schema with type, bounds, description, and default behavior. The description adds no extra meaning around 'days', but with 100% schema coverage the parameter semantics are already sufficient.

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 description names a specific action (get) on a specific resource (upcoming assignments and assessments), narrows scope to ALL Blackboard courses, and adds organization by due date. It clearly answers what the tool does and is easily distinguishable from siblings like list_courses or get_grades.

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?

It explicitly frames this as the one call for 'what do I have due?', giving clear context for when to use it. However, it doesn't name alternatives or state when NOT to use it, such as when results for a single course are needed.

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