List Course Topics

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

Annotations already declare the operation read-only, idempotent, open-world, and non-destructive. The description adds useful context about what is returned and how topics are used, but it does not disclose additional behavioral traits such as pagination, ordering, or potential error cases. No contradiction exists.

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 concise and front-loaded with the core purpose. The extra sentences about what topics represent and how to use topic IDs add value without excessive length, though the Args block duplicates schema details.

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 list operation, the description covers the return content (topicId and name), the relationship to sibling tool classroom_list_coursework, and the role of the main parameter. The annotations cover safety, so no critical behavioral information is missing for correct invocation.

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%: course_id and response_format are both documented with types, defaults, and source guidance. The description's Args section mostly restates schema information, so it adds little beyond what the schema already provides.

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 states a specific verb and resource: 'List all topics ... within a course.' It also clarifies what topics are in the teacher/classroom context, making the tool's purpose unambiguous and distinguishable from sibling listing tools like classroom_list_coursework or classroom_list_courses.

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?

The description clearly implies when this tool is useful: to obtain topic IDs for a course, and then pass each topicId to classroom_list_coursework. It provides actionable usage context but does not explicitly state when not to use it or compare it against alternatives like classroom_list_announcements.

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