sincronizar_materia

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

With no annotations, the description carries the behavioral burden and discloses important traits: it downloads only new files to a local folder, lists external links without downloading them, and syncs all active subjects when `materia` is empty. It does not cover permissions, overwrite behavior, or error handling, but the core side effects are transparent.

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 two sentences, front-loaded with the main action and followed by the key scope and exclusion. Every sentence adds useful information without repetition.

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 one-parameter sync tool with an output schema, the description covers the essential invocation semantics and the main behavioral caveat about external links. It leaves out some operational details such as destination folder handling and permissions, but is otherwise complete enough to select and call the 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 description coverage is 0%, so the description must compensate for the single `materia` parameter. It usefully explains that an empty value means all active subjects, but it does not clarify the expected format of a non-empty subject value, such as ID versus name.

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 uses a specific verb and resource: 'Descarga solo los archivos nuevos de una materia'. It clearly scopes the operation to new files and explains the all-subjects case, though it does not explicitly contrast itself with sibling tools such as descargar_archivo or listar_archivos.

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?

It explains when the empty `materia` value applies: all active subjects are synced. However, it does not state when to use this bulk sync tool versus alternatives like descargar_archivo or listar_archivos, so usage guidance is implied rather than explicit.

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