Get Course Sections

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

No annotations exist, so the description must bear the full behavioral burden. It states the tool lists routes but does not disclose authentication needs, rate limits, potential side effects (though likely read-only), or the structure of the response. The presence of an output schema helps, but the description itself lacks detail.

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, clear sentence without extraneous words. It is front-loaded with the verb and resource. However, it could be slightly more informative without becoming verbose.

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?

Given the tool has one parameter, an output schema, and many siblings, the description is too brief. It does not explain what 'direct course routes' are, how to identify them, or any prerequisites. The output schema covers return values, but the description omits important context for usage.

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?

With 0% schema coverage for the single 'course' parameter, the description should clarify its meaning or format. It does not. The description adds no value beyond the schema's type 'string', leaving ambiguity about what value to pass.

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 uses a specific verb 'List' and a specific resource 'direct course routes exposed on the Ninova course home page', which clearly distinguishes this tool from siblings that handle other course data (e.g., announcements, assignments). It leaves no ambiguity about what the tool returns.

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?

No guidance is provided on when to use this tool versus alternatives like 'crawl_course' or other get_course_* tools. The description implies its use in listing course sections but offers no exclusions or context for selection.

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