Sync All Courses

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

Core behavior (fetch, store, return changes) is described, but missing details on authentication requirements, side effects beyond storing, and rate limits. Annotations are absent, so description carries weight.

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?

Single sentence, 18 words, no waste. Information-dense and 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?

With output schema present, description doesn't need to detail return format. However, lacks parameter documentation and does not explain the 'tracking snapshot' state management.

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 description coverage is 0%, yet the description does not explain any of the three parameters (course_limit, include_files, file_max_depth). This is a critical gap.

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 verb 'fetch', resource 'all visible courses', and the outcome of storing a snapshot and returning changes. It distinguishes from siblings like 'get_courses' and 'diff_snapshot'.

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?

Usage context is implied (periodic sync), but no explicit guidance on when to use vs. alternatives like 'diff_snapshot' or 'get_courses'.

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