Get homework and exams

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

The description discloses specific behavioral traits beyond the readOnlyHint and openWorldHint annotations: items marked done are excluded unless include_done is true, and each item includes certain fields. This gives agents precise expectations of results and side effects.

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, well-structured sentence that front-loads the primary purpose and default date range, then compactly covers filters and output. No unnecessary words; every clause adds 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?

With an output schema present and five optional parameters, the description adequately covers defaults, filtering behavior, and return contents. The missing context is the 'student' parameter's purpose, which could affect correct usage in multi-student accounts.

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?

Even though the schema description coverage signal is 0%, the description provides meaningful semantics for start_date, end_date, kind, and include_done, including defaults and filtering effects. The only unresolved parameter is 'student', which is left unexplained.

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 clearly states the resource (homework and announced exams), the date range filtering with explicit defaults, and the output format. It distinguishes from sibling tools like get_timetable and get_events by focusing specifically on homework/exam items and their metadata.

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 provides clear context on when to use the tool (for homework and exam items due in a date range) and explains default behavior and filters. However, it does not explicitly mention alternatives or exclusions (e.g., when to use get_timetable instead), so it falls short of the highest bar.

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