지난 확인 이후 변경 사항

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

The description transparently explains the snapshot mechanism, including that the first run only creates a baseline and that 'update_snapshot' controls whether the snapshot is refreshed. This complements the readOnlyHint=false annotation and gives the agent a clear picture of state changes.

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 concise and front-loaded, stating the main purpose first and then explaining the snapshot behavior and optional parameter. No redundant or vague language is used.

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 there is no output schema, the description provides sufficient context for an agent to decide when and how to invoke the tool. It covers the scope of changes, snapshot mechanics, and the key 'since' parameter, making it complete for practical use.

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?

All three parameters are described in the schema, and the description adds meaningful context: 'since' is the baseline time (defaulting to snapshot), 'course_id' filters to a specific course, and 'update_snapshot' controls snapshot refresh. The coverage is complete and the semantics are clear.

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 shows new announcements, new assignments, assignments with changed deadlines/submission status, and new course materials since the last check. It also explains the snapshot behavior and the optional 'since' parameter, distinguishing it from single-entity retrieval tools.

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 clear context on when to use the tool (after a previous check, first run creates a snapshot, 'since' can override the baseline). However, it does not explicitly name alternative tools or state when not to use it, so it falls slightly short of explicit alternative guidance.

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