moodle_course

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

No annotations are provided, so the description must fully disclose behavior. It only states what data is returned, without mentioning that it is a read-only operation, any required permissions, side effects, or rate limits. The agent cannot infer safety or mutability from this description alone.

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 short sentence that immediately states the tool's output. It is appropriately concise and front-loaded, with no wasted words. Could be slightly more structured but is effective.

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?

The tool has a single required parameter and an output schema (not shown), so complexity is low. The description covers the core output (sections and activities) but misses context like authentication requirements, data source freshness, or error conditions (e.g., invalid course_id). Adequate but not thorough.

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% (no parameter descriptions in schema). The description does not explain the course_id parameter at all; it only implies it via the tool name and description. While the parameter type is obvious, the description adds no value beyond the schema's type definition, failing to compensate for the lack of schema documentation.

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 it retrieves a Moodle course's contents (sections and activities) with specific attributes (id, title, kind, url). This verb ('get') is implied, and the resource is distinct from sibling tools like moodle_courses (list all courses) and moodle_activity (single activity).

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 guidance on when to use this tool vs alternatives. The description implies use when needing course contents, but does not mention prerequisites (e.g., valid course_id) or when it might be inappropriate. Sibling tool names provide some implicit context but the description itself lacks direct usage advice.

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