Get Calendar

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

The annotations already declare this is a safe read-only operation, and the description adds useful behavioral context about data completeness: exam and assignment dates depend on teacher entry and the syllabus should be consulted for the full picture. It does not explain pagination or how the page parameter affects results, which keeps it from a 5.

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 purpose is front-loaded in the first sentence, followed by the sibling comparison and then the data completeness caveat. All three sentences carry useful information with no redundant restatement of the title.

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?

The description explains the calendar contents and the major data limitation, which is helpful for a tool with no output schema. However, it omits parameter behavior for page and range, so an agent still lacks guidance on how to control the returned time window or pagination.

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%, so the description carries the burden of explaining the two parameters. It does not explain what 'page' controls or clarify the meaning of the 'range' enum values, leaving parameter usage largely inferential.

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 gives a specific verb and resource: retrieve the day-by-day calendar. It enumerates the relevant contents (classes, holidays, day swaps, cancelled classes, exams, deadlines) and explicitly distinguishes the tool from get-schedule for day-specific information.

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?

It explicitly says to prefer this over get-schedule for what happens on a given day, which gives a clear routing rule. It also warns that exam and assignment dates only appear if the teacher entered them on Lea, so the agent knows the tool may not be complete.

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