get_schedule_changes

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

No annotations are provided, so the description carries the full burden. The verb 'get' implies a read-only operation, but nothing is disclosed about return format, pagination, or date handling semantics, leaving significant behavioral ambiguity.

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 extremely short — a single sentence. While concise, it is under-specified rather than appropriately sized, providing no front-loaded context or useful elaboration.

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 no annotations, no output schema, and a 6-parameter input at 0% schema coverage, this description is completely inadequate. It fails to convey the tool's data source, filtering options, or expected result, making it almost impossible for an agent to use correctly.

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?

The input schema has 6 parameters with 0% description coverage in the schema, and the description provides no explanations for any parameter. It does not even clarify the required from_date and school_code parameters, leaving all parameters opaque.

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 states the resource ('schedule change events') and a verb ('get'), which is clear at a basic level. However, it does not specify the scope (e.g., by class, teacher, or date range) and only marginally distinguishes from sibling tools that also retrieve schedule data.

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?

There is no guidance on when to use this tool versus alternatives like get_class_day or get_teacher_week. It does not mention required parameters, date range conventions, or any exclusions.

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