Get Weekly Schedule

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

With no annotations, the description carries the burden of behavioral disclosure. It does reveal that the schedule is sorted by day and start time, which is useful, and 'Return' implies a read-only operation. However, it does not explain what happens when semester is null, whether authentication is required, or how failures are surfaced.

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 one sentence with no filler; the core action, object, and output ordering are presented directly. Every word earns its place and the structure is appropriately front-loaded.

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 simple one-parameter read tool with an output schema, the description is nearly adequate. However, the optional semester parameter is left semantically unexplained, and the lack of any distinction from obs_public_get_schedule leaves an ambiguity an agent may need to resolve.

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 single parameter has zero schema description coverage, so the description must compensate. It only says 'for one semester,' which weakly hints at the semester parameter, but it never clarifies accepted values, the default behavior, or what a null semester means.

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 ('Return') and resource ('weekly class schedule for one semester') and adds an ordering detail, so an agent can distinguish it from exam or course schedule tools. However, it does not explicitly distinguish this from the sibling obs_public_get_schedule, so it is clear but not fully differentiated.

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?

The description gives no when-to-use or when-not-to-use guidance. It does not mention that obs_public_get_schedule may be the public alternative, nor does it specify when the optional semester parameter should be supplied.

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