moodle_course_tree

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

Annotations are absent, so the description must convey behavioral traits. 'Show' clearly implies a read-only operation, but the description does not mention prerequisites, potential errors, or side effects, leaving some ambiguity. Despite this, it is not misleading and adequately signals a safe retrieval.

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 a single, front-loaded sentence that immediately conveys the action and object. There is no redundant or extraneous text, making it optimally concise.

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?

Given the tool's simple nature and the presence of an output schema, the description covers the core purpose. However, the unexplained 'site' parameter and lack of any error-condition context mean it is not fully complete, though adequate for basic usage.

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?

With schema description coverage at 0%, the description must compensate. It clarifies course_id as the target identifier, but provides no explanation for the optional 'site' parameter, leaving a gap in understanding for multi-site setups. This partial compensation is insufficient for full parameter 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 states a specific verb ('Show') and resource ('sections and modules with file counts') for a given course id, making its function clear. It distinguishes from sibling tools like course_download or courses_list by focusing on the structural view of one course.

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?

The description provides no information about when to prefer this tool over alternatives such as moodle_course_download or moodle_course_sync. It lacks any exclusions or context on typical use cases, offering only a bare functional statement.

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