connects_course

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

The annotations already communicate read-only, idempotent, non-destructive behavior, so the description does not need to repeat those. It adds helpful context that the call targets a course section and depends on an ID from connects_courses, but it does not disclose pagination behavior or how the section parameter affects the result.

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?

A single sentence delivers the action, resource, and prerequisite with no filler. The key information is front-loaded and every word contributes.

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 presence of an output schema and strong annotations covers safety and return-value concerns, making the minimal description usable for straightforward calls. However, the section enum values and pagination parameters are left unexplained, so the definition is adequate but not fully complete for correct invocation in all cases.

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 description coverage is 0%, so the description must compensate, but it only explains the provenance of course_id. It does not add meaning for limit, offset, or the section enum, leaving the agent to rely on bare schema types and defaults.

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 names a specific action ('Read') and resource ('Connects course section'), and it clarifies that the course ID comes from connects_courses. This makes it easy to distinguish from sibling list tools like connects_courses and from tools for other platforms such as blackboard_course.

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?

It clearly states the intended use case: read a section of a Connects course using a course ID obtained from connects_courses. It does not explicitly state exclusions or alternative tools, but the prerequisite/source relationship gives enough contextual guidance.

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