get_upcoming_schedule

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

No annotations are provided, so the description carries the behavioral disclosure burden. The 'get' verb implies a read-only operation and the time window is stated, but the description does not clarify whether 'today' is included, how results are ordered, or what fields the schedule contains. For a simple read tool this is acceptable but not thorough.

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 that states the action, resource, and time scope without unnecessary words. It is front-loaded and every word 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, one-parameter read operation, the description plus schema is mostly sufficient. The main gap is the ambiguous boundary of 'upcoming' and 'next N days' — whether the range starts today or tomorrow — which could affect correct invocation. No output schema exists, so a brief note on the response format would improve completeness.

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 only parameter, 'days', has full schema description coverage (default, min, max), so the schema already explains it well. The description's 'N days' loosely maps to this parameter but adds no additional semantic detail beyond what the schema provides.

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 the action ('Get') and resource ('upcoming lecture schedule') with a specific time window ('next N days'). It is distinguishable from get_today_schedule and get_next_lecture, though it does not explicitly differentiate itself from the broader get_schedule sibling.

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 phrase 'next N days' implicitly signals this tool is for range-based upcoming schedules, contrasting with today-only or next-single-lecture tools. However, there is no explicit when-to-use guidance or mention of alternatives, so the agent must infer the right context.

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