check_module_updates

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

No annotations are provided, so the description carries the full behavioral burden. It doesn't say whether this is a read-only check, whether 'checking' mutates a seen/unread state, whether it requires authentication, or what the result contains. 'Check for new' implies read but leaves mutation semantics ambiguous.

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?

A single, front-loaded sentence with no filler. It is appropriately sized, though it wastes the opportunity to disambiguate against siblings in the same breath.

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 tool with no annotations and no output schema, the description should clarify return content (e.g., new materials vs. announcements) and its relationship to get_announcements. Instead it leaves the module-vs-course scope mismatch unresolved, so the agent cannot be confident about what it will get back.

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 100% and the single courseId parameter is fully documented in the schema, so the baseline is 3. The description adds no syntax or format detail, and its mention of 'module' conflicts with the course-level parameter, which adds mild confusion rather than clarity.

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 gives a clear verb+resource ('check' + 'new materials or announcements in a module'), so the agent knows the general intent. However, it does not differentiate from the sibling get_announcements, and it says 'a specific module' while the only parameter is courseId, blurring the scope of what is actually checked.

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 when-to-use guidance is given. With siblings like get_announcements, sync_module, and list_modules present, the agent has no stated criteria for choosing this tool over those, and no prerequisites (auth, session) are mentioned.

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