List Course Tabs

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false, and openWorldHint, so the description repeats little by saying 'Read-only'. It does add value beyond annotations by scoping the result to what is 'visible to you', implying permission/enrollment-dependent output, which is real behavioral context. It stops short of stating ordering or what happens if the course is inaccessible.

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 plus a fragment, zero waste, and the core purpose is front-loaded ahead of the workflow advice. Every sentence earns its place.

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 one-parameter read tool with full annotation coverage, the description covers purpose, returns at a high level, and when to call it. Only the exact return shape (tab ordering, enabled flags) is unspecified, which is minor since there is no output schema.

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% and the single course_id parameter is fully documented in the schema, including the pointer to list_courses as the source. The description adds no parameter-level detail, so the baseline of 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 (List) and resource (navigation tabs), with concrete examples of what a tab is (Home, Assignments, Files, Quizzes). An agent can distinguish this from sibling tools like get_course_settings or list_course_files without opening the 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?

Explicitly tells the agent to check this first to see whether a feature such as Files or Pages is enabled before calling its tools. That is a named precondition plus the alternative route, not inferred guidance.

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