learnus_get_course

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so the safety profile is fully covered. The description adds only that the output is a 'normalized structure and activities', which hints at the response shape but does not cover pagination, result size, or what 'normalized' means. With annotations carrying the burden, this is adequate but not rich.

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?

Three short sentences: purpose first, then positive usage trigger, then negative exclusions. Every sentence earns its place with no redundancy.

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?

Single required parameter, no nested objects, no output schema, and the description signals the return contents ('normalized structure and activities'). Nothing essential is missing for correct invocation, though the absence of an output schema leaves the exact return shape underspecified.

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 coverage is 100% and the schema's own description explains courseId must be an exact Moodle course ID from a LearnUs course tool. The description's phrase 'one known LearnUs course' reinforces this but adds no syntax or format detail beyond the schema. Baseline 3 applies.

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?

States a specific verb (Gets) and resource (one known LearnUs course) plus the returned scope (normalized structure and activities). It is immediately distinguishable from learnus_list_courses, which is the sibling covering discovery of many courses.

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?

Gives an explicit trigger condition ('when an exact course is known and the user asks for that course's contents or structure') and explicit exclusions ('Do not use it to discover all enrolled courses or to fetch full assignment/announcement details'), routing the agent to learnus_list_courses, learnus_get_assignment, and learnus_get_announcement.

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