get_course

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

No annotations are provided, so description must fully cover behavior. It states what details are returned (full name, short name, summary, etc.) which is good, but it does not disclose potential side effects, authentication requirements, or rate limits. For a read-only fetch, it is partially 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?

Description is one sentence followed by a list of returned fields. It is concise and front-loaded. Could be slightly more structured (e.g., bullet points) but is clear and to the point.

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 simple fetch tool with one parameter and no output schema, the description is adequate but lacks some completeness. It lists returned fields but does not explain how to interpret them (e.g., date formats), or error conditions (e.g., invalid courseid). There is no output schema to supplement.

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 covers the single parameter 'courseid' with type and description. The description adds semantic meaning by explaining what the tool returns, which helps the agent understand the purpose. Since schema coverage is 100% and there is only one param, the description provides additional context.

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?

Description uses specific verb 'Fetch' and resource 'complete details for a single Moodle course', clearly distinguishing from sibling tools like 'list_courses' which retrieves a list, and 'search_courses_by_name' which searches. The tool's purpose is unambiguous.

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 versus alternatives (e.g., 'list_courses' or 'search_courses_by_name'). Usage must be inferred from the tool name and description. It's assumed useful for getting detailed info about one course, but no exclusions or context are given.

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