Get Course Info

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

Annotations already declare readOnlyHint=true and destructiveHint=false, and an output schema exists, so the safety profile and return shape are covered elsewhere. The description adds only that the payload includes identity and teacher names — useful, but no auth, caching, or error context beyond that.

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 short sentences, front-loaded with the action and then the payload contents. No wasted words, though nothing is stated about term scoping despite an optional term_id.

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?

With readOnly annotations, a full output schema, and 100% schema description coverage, most of the burden is carried by structured fields. The description is complete enough to call correctly, though it omits how the optional term_id affects which offering is resolved.

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 course_id description already explains the group-number format and the 'always required' caveat. The description adds nothing about either parameter, so the 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 ('Retrieve') and resource ('info about a specific course') and names what is returned (course identity, teacher names). It is clear on its own, but it never distinguishes itself from close siblings like get-courses-summary, get-course-people, or get-teachers.

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?

There is no guidance on when to call this versus get-courses-summary (listing courses) or get-course-people / get-teachers (which also surface teacher data). The agent must infer the selection criteria from sibling names alone.

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