moodle_sync_all

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

With no annotations, the description must disclose behavioral traits. It only notes that the operation is long-running, but omits effects (e.g., what syncing does, whether it downloads content, modifies state, requires authentication, or is reversible). This is insufficient for a sync operation.

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 extremely concise: two short sentences ('Sync all enrolled courses. Long-running.') with no wasted words. It is well-structured and easy to parse.

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 long-running sync operation with no annotations and undocumented parameters, the description is incomplete. It lacks context about what syncing involves, potential side effects, duration expectations, or how to handle the operation. The presence of an output schema does not compensate for the missing behavioral guidance.

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?

The schema has two parameters ('out', 'site') with 0% description coverage and no descriptions in the schema. The description adds no meaning to either parameter, leaving the agent without any understanding of how to use them.

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 states a specific action ('Sync') and resource ('all enrolled courses'), clearly distinguishing from a single-course sync tool like moodle_course_sync. However, it does not explicitly differentiate from siblings or elaborate on what 'sync' entails, though the scope is clear.

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 guidance on when to use this tool versus alternatives. The phrase 'Long-running' hints that it is heavy, but there is no explicit when-to-use, prerequisites, or exclusions. Sibling tools like moodle_course_sync are not mentioned.

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