List Course Sections

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

Annotations already declare readOnlyHint/idempotentHint/openWorldHint/destructiveHint=false, so the safety profile is covered. The description adds quota behavior beyond that: "every page counts against the API quota" and "supports bounded all_pages" — genuinely useful operational context about rate/cost implications.

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?

Three short sentences, front-loaded with the purpose and quota constraint. However, the opening sentence duplicates the tool name/title and carries no added value.

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?

With no output schema, the description could say something about what a returned section contains, and it never clarifies list-vs-get selection. Quota and bounded-pagination context is present, but return-value shape and sibling routing are absent.

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 schema already documents all 7 parameters (page, sort, account, per_page, space_id, all_pages, max_items), including the all_pages quota note. The description echoes rather than extends this, so the 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?

"List Course Sections" restates the tool name/title almost verbatim, so the purpose is clear (list, course sections) but the description adds no differentiation from siblings like get_course_section or list_course_lessons. The appended "Reads community data" hints at scope but does not distinguish this tool's role.

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?

There is no when-to-use guidance, no mention of alternatives (get_course_section, list_course_lessons, search), and no prerequisites or exclusions. "Reads community data" is context, not usage guidance.

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