get_course

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

Annotations declare readOnlyHint and openWorldHint. The description adds behavioral context beyond annotations: it specifies that by default only 'term' and 'total_students' are returned, and that the include parameter replaces the default set. This provides useful behavioral insight not present in annotations.

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?

Two sentences with zero wasted words. The most critical information is front-loaded (what the tool does), followed by default behavior and customization. Efficient and well-structured.

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 adequately covers input behavior but does not describe the return value (e.g., full course object) despite lacking an output schema. Given the tool's simplicity and annotations, it is functional but could be improved by noting the response structure.

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% with descriptions for all parameters. The description adds meaning by explaining that include replaces the default fields and by listing example values. This goes beyond the schema's basic type/enum descriptions.

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 'Get details for a single course,' which is a specific verb+resource combination. It clearly distinguishes from siblings like 'list_courses' (multiple courses) and 'get_course_activity_stream' (activity stream vs course details).

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 explains default behavior (term and total_students) and how to customize via include parameter. However, it does not explicitly state when to use this tool versus alternatives like get_course_structure or list_courses. The context from sibling names implies usage, but explicit exclusions are missing.

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