canvas_sync_course

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

With no annotations, the description carries the full burden and largely fails: it does not say whether the sync overwrites existing vault notes, whether it is incremental or destructive, whether it can be rate-limited or long-running. The enumeration of synced content gives some sense of write scope, but the critical mutation profile is undisclosed.

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; the scope comes first and the content enumeration follows. It is efficient, though the terseness contributes to the missing behavioral detail.

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?

A multi-parameter mutation tool with zero annotation coverage, no output schema, and 0% parameter documentation needs substantially more than one sentence. The absence of any explanation of dry_run or of overwrite behavior makes the definition insufficient for safe invocation.

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% across 5 parameters. The listed content types loosely hint at download_files, include_announcements and include_discussions, but dry_run — the highest-stakes parameter — is never mentioned, and there is no explanation of defaults or of course_id semantics.

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?

States a specific verb ('Sincroniza') and resource ('un curso completo al vault') and enumerates the content types pulled in (archivos, tareas, páginas, módulos, anuncios, discusiones). This differentiates it from canvas_sync_all_courses by scope, though the contrast is only implicit.

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 when-to-use guidance, no prerequisites, and no alternatives named. The agent must infer from the name/description that this is the single-course counterpart to canvas_sync_all_courses, and nothing warns when it should avoid a full sync in favor of canvas_download_course_files or canvas_course_inventory.

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