Semester Wrap Up

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

The annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description repeats 'Read-only' and adds useful context about access closure, but does not disclose data freshness, permissions, or other behavioral details beyond the annotations.

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?

The purpose is front-loaded in a single compact sentence followed by a useful alternative-use note. Every phrase contributes to scope or expected contents, with no filler.

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 input parameters and no output schema, the description carries the burden of explaining what the result contains. It does so by listing the checklist items and the course-access timeframe, which is sufficient for an agent to understand the tool's output at a high level.

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 has zero parameters, so there are no parameter meanings to explain and the baseline is 4. The description correctly avoids irrelevant parameter detail for a no-argument aggregate tool.

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 clearly identifies an end-of-term checklist scoped to every active course and enumerates the specific contents: current and final grades, missing work, remaining due items, and days until course/file access may close. It distinguishes itself from export_all_courses for saving copies, but does not explicitly differentiate from similar siblings like semester_snapshot or get_week_ahead.

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?

Use is clearly framed as end-of-term and active-course scoped, and the description names export_all_courses as the alternative when the user wants to save copies. It does not state when not to use this tool or how it differs from other overview tools.

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