get_teacher_schedule

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

Annotations already declare readOnlyHint, openWorldHint=false, and destructiveHint=false, so the safety profile is covered. The description adds accepted identifier formats and date-filtering behavior, but does not disclose permissions, rate limits, or return characteristics beyond what annotations provide.

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 three sentences, front-loaded with the main purpose, followed by parameter acceptance and filtering support. Every sentence carries useful information 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?

For a read-only schedule lookup with full schema coverage and safe-operation annotations, the description is largely complete for invocation. It does not describe the return shape, but no output schema exists and the core purpose plus parameters are sufficiently covered.

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, but the description meaningfully adds that a full name ('ФИО') is accepted for the teacher parameter beyond the schema's surname/urlId examples. It also gives a concrete date example ('2026-09-07'), though the days parameter is only briefly summarized as a range.

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 and resource: 'Получить расписание занятий преподавателя БГУИР.' It clearly distinguishes this from sibling tools such as get_group_schedule by specifying that the schedule is for a teacher, not a group. An agent can identify the tool's purpose without opening the schema.

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 description explains what the tool accepts and its filtering capabilities, but gives no explicit when-to-use guidance, no prerequisites, and no routing to alternatives like search_teachers or get_teacher_profile. The agent must infer when this tool is appropriate relative to siblings.

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