schoology_list_sections

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

No annotations are provided, so the description carries the full behavioral burden. It implies a read-only listing and signals a data merge with StudentVUE grades, but it does not disclose authentication requirements, pagination behavior, rate limits, or return format details.

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 single sentence is front-loaded and wastes no words. It is appropriately sized for a zero-parameter listing tool, though it is terse enough that important usage context is absent.

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 description gives the core purpose and a hint about returned data ('sections with official StudentVUE course grades'), which is useful because no output schema exists. However, it omits usage context, authentication expectations, and any detail about the shape or volume of returned sections and grades.

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?

The tool has zero parameters, and the rule baseline for zero parameters is 4. The description adds no parameter information, which is acceptable because there is no input schema to clarify.

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 ('List') and resource ('enrolled Schoology sections') and adds that results include official StudentVUE course grades. It is clear, but it does not explicitly differentiate itself from sibling tools like studentvue_get_grades or schoology_get_section_updates.

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 explicit when-to-use guidance, no conditions for choosing this tool over alternatives, and no mention of prerequisites. The only implied guidance is the bare 'List' operation itself.

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