Daily Briefing

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

Annotations already declare readOnly, idempotent and non-destructive, so the safety profile is covered. The description adds genuine behavioral content beyond that: it enumerates exactly what is bundled and defines the time windows ('today and tomorrow', 'last day'), which tells the agent this is a composite aggregation rather than a raw list. It does not mention scope across courses or any volume limits, keeping it short of a 5.

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?

One sentence, front-loaded with the framing 'Today at a glance' and then a compact content list. Every clause names a distinct data category, so nothing is 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 zero parameters, full annotation coverage and an output schema that defines the return shape, the description supplies everything an agent needs to decide and call. The only gap is that it never clarifies cross-course scope or how it relates to the overlapping aggregate siblings.

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 no parameters, so there are no semantics to explain and the baseline of 4 applies. Nothing in the description misrepresents the empty input schema.

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 states a concrete aggregate purpose: a single-call digest covering today's classes/events, due items, missing work, recent grades, unread announcements and inbox count. That is far more specific than its title, though it never names the sibling aggregates (get_week_ahead, get_all_unread, semester_snapshot) it overlaps with, so differentiation is left to inference.

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?

Usage is only implied by the framing 'Today at a glance' – an agent can guess this is a morning-check summary rather than a filtered list. There is no explicit when-to-use versus get_week_ahead or get_all_unread, and no statement of when this is the wrong choice.

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