ScheduleGetSchoolSchedule

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds the date-range scoping but does not mention pagination, filtering behavior, or what the response contains; nothing contradicts 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 description is a single front-loaded sentence with no filler or redundant wording. It is concise, though it achieves that by omitting potentially useful context.

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 seven parameters, a nested object, no output schema, and many sibling schedule tools, this description is too thin. It does not mention filters, pagination, or how to distinguish this tool from ScheduleGetTeacherSchedule or ScheduleGetPupilSchedule, so an agent would need to inspect schemas and names to invoke it correctly.

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 description coverage is 86%, so most parameters already carry meaningful descriptions such as filters by group, pupil, and teacher. The description only adds the date-range idea, which maps to bodyDateStart and bodyDateEnd, but does not compensate for the undocumented pagination parameters.

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 clear verb and resource: 'Get the school schedule for a date range.' However, it does not differentiate this from sibling tools like ScheduleGetTeacherSchedule, ScheduleGetPupilSchedule, or ScheduleGetSchoolWeekWorkTime, leaving some ambiguity about what 'school schedule' specifically covers.

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?

There is no guidance on when to use this tool versus the many schedule-related siblings, and no exclusions or alternative conditions are provided. The only usage signal is the name and the date-range phrase, which is not enough to route an agent correctly.

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