Get My Courses

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds the return shape (names, codes, IDs), but says nothing about pagination, ordering, or whether inactive/future enrollments appear by default.

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 tight sentences, front-loaded with the resource and payload, followed by usage triggers. No filler or restatement of the title.

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 one-optional-param read tool with no output schema, the description covers what is fetched and when to reach for it. It could be slightly more complete by noting the default active-only filtering behavior that the schema documents.

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 100%, so the single activeOnly parameter and its server-default behavior are already fully documented. The description does not mention activeOnly at all, so it adds no meaning beyond the schema; 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 (Fetch) and resource (your enrolled Brightspace courses) and enumerates the payload (names, codes, IDs). This differentiates it cleanly from siblings like get_my_grades, get_assignments, and get_course_content without needing to open any schema.

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?

Supplies concrete trigger phrasings ("their courses", "enrolled classes", "what they're taking this semester") and routes the agent to this tool when a course ID is needed for other queries. No explicit when-not clause, but the trigger list is specific enough to drive selection.

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