Get Course

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

With no annotations provided, the description carries full responsibility for disclosing behavior. It only says 'Return', implying a read operation, but does not mention error behavior (e.g., not found), permission requirements, or the structure of the returned course object. This is a significant gap for a tool without annotation coverage.

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, tightly worded sentence with no redundant information. It is front-loaded with the action and object, making it efficient for an agent to parse quickly.

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 no output schema, the description should at least hint at what is returned (e.g., course details) or error cases. It does neither, leaving the agent uncertain about the response format and failure modes. This is inadequate given the absence of both annotations and an output schema.

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?

The schema already describes course_id as 'Canvas course ID' with 100% coverage, so the description adds no extra meaning. The baseline of 3 applies because the schema handles parameter documentation adequately; the description does not need to repeat it.

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 'Return' and resource 'one Canvas course by ID'. It clearly indicates the tool fetches a single course, distinguishing it from list_courses by the ID qualifier, though it does not explicitly name alternatives. It is not a tautology because 'by ID' adds operational meaning.

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 guidance on when to use this tool versus alternatives like list_courses. It does not mention any prerequisites, context, or exclusions, leaving the agent to infer usage from the name and parameter alone.

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