OBS Schedule

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

No annotations are provided, so the description must fully disclose behavioral traits. It states 'Read' indicating a read-only operation, but lacks details on semester parameter behavior (e.g., default value handling), rate limits, or any side effects. Minimal disclosure.

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 sentence, but it lacks necessary details about parameters and behavior. Under-specification reduces usability despite being short.

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?

Given the tool has an output schema, the description should clarify the input and output semantics. It mentions 'weekly class schedule and final exam calendar' but does not explain the semester parameter or what the output contains. Incomplete for a query 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 coverage is 0%, so the description should compensate for the single parameter 'semester'. It does not explain acceptable values, format (e.g., '2024-1'), or behavior when null. No added meaning beyond the schema.

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 tool reads a weekly class schedule and final exam calendar for a semester. It uses a specific verb 'Read' and specifies the resource, distinguishing it from sibling tools like obs_get_attendance or obs_get_course_grades.

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?

No explicit guidance on when to use this tool over alternatives. While the purpose is clear, there are no when/when-not statements or comparisons to siblings like obs_get_attendance or obs_get_course_grades. Usage is implied but not elaborated.

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