get_teacher_week

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

With no annotations, the description must fully disclose behavioral traits. It only restates the fundamental action ('Get a teacher week schedule') without mentioning date format, week definition, return structure, or any error conditions. The read-only nature is implied but not enriched with useful context.

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, grammatically clean sentence with no filler, but it is under-specified to the point of being nearly tautological. Conciseness is acceptable, but the lack of substance limits its value.

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 tool with 3 required parameters, no annotations, and no output schema, this one-sentence description is insufficient. It does not explain the return format, how the date parameter defines the week, or when this tool is appropriate given the sibling tools.

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 0%, and the description adds no meaning to the three parameters (school_code, teacher_id, date). It does not explain what 'date' represents, what school_code and teacher_id refer to, or how they relate to the schedule retrieval.

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 resource ('a teacher week schedule'), clearly indicating the tool's purpose. It does not explicitly differentiate from sibling tools like get_teacher_day or get_class_week, but the resource is unmistakably a teacher's weekly schedule.

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?

No guidance is provided on when to use this tool versus alternatives such as get_teacher_day or get_class_week. There are no context clues, exclusions, or prerequisites beyond the basic purpose.

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