ScheduleGetTeacherSchedule

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

The annotations already establish that this is a read-only, non-destructive operation, so the description does not need to restate that. It adds the timezone interpretation context but does not disclose details like default timezone behavior or what schedule entries look like.

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 description is a single, well-structured sentence that front-loads the core action and scope. It contains no filler, redundancy, or unnecessary detail.

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 output schema, the description could have explained what the returned schedule contains or how the timezone parameter is handled. The tool is simple enough that the description is minimally viable, but some invocation-relevant details, especially the integer timezone format, remain unexplained.

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 100%, so the baseline is 3 even though the schema descriptions are shallow ('integer (required)'). The description adds meaning by tying dateStart/dateEnd to a date range and timezone to timezone interpretation, but it does not clarify the timezone format or default behavior.

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 uses a specific verb ('Get') and identifies the exact resource ('a teacher's schedule') with date-range and timezone scoping. This clearly distinguishes it from sibling tools like ScheduleGetPupilSchedule, ScheduleGetSchoolSchedule, and ScheduleGetTeacherWeekWorkTime.

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 resource scope makes the intended use case reasonably clear, but the description does not explicitly state when to prefer this tool over alternatives or when not to use it. Usage guidance is implied rather than stated.

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