get_course

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false. The description adds the HTTP method (GET) and a READ-ONLY label, which is consistent but not substantially beyond annotations. It does not disclose additional behavioral details like authentication or response structure.

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, using three short sentences to convey purpose, HTTP method, and behavior. It front-loads important flags (READ-ONLY, resource type) and contains no unnecessary words.

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 description states the tool returns 'information about the course' but does not specify what fields or structure, given there is no output schema. For a simple get operation, this is adequate but could be more informative about the return content.

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 description merely restates the parameter as 'provided course id' without adding meaning beyond the schema's description 'Unique identifier of the course'. No extra semantics are provided.

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 explicitly states 'Get a course' and 'Returns information about the course specified by the provided course id.', making the action (get) and resource (course by id) clear. This distinguishes it from sibling tools like get_courses (list) and create_course (mutation).

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 implies usage for retrieving a single course by id but does not provide explicit guidance on when to use this versus alternatives like get_courses or get_contents_course. No exclusions or contexts are mentioned.

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