Class-free days

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the description's added value is interpretive: it warns that type_id is an opaque code rather than a name and that a day lacking lesson numbers is not automatically free all day. Those two caveats directly prevent misreading of results, which annotations and schema cannot convey.

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?

Two tight sentences with the purpose front-loaded and the caveats trailing. The type_id remark is slightly cryptic in isolation but every clause carries information.

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?

An output schema exists, so return shape need not be described, and the description covers scope plus the two most likely misinterpretations of the returned data. Account scoping and paging are handled by the schema, leaving no material gap for a 3-parameter read tool.

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 100%, and limit, cursor and account_alias are all documented in the schema, so baseline 3 applies. The description adds nothing about pagination or account scoping; its only semantic note (type_id) refers to output, not to an input parameter.

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?

States a specific verb and resource ('List the class's days and lesson ranges without classes') and gives concrete examples (holidays, school free days). It is clearly distinct from data-heavy siblings like get_timetable or get_attendance, though it never names an alternative explicitly.

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?

Usage is implied by the phrase 'days ... without classes', so an agent can infer this is the query for non-instructional days. However, there is no when-to-use / when-not-to-use guidance relative to get_timetable or get_completed_lessons, and no prerequisites stated.

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