list-onenote-section-group-sections

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

Annotations already indicate a safe, read-only, idempotent operation. The description adds valuable behavioral context by specifying default ordering ('newest-modified first') and automatic pagination beyond 100 items, which is not conveyed by the annotations.

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 a single, front-loaded sentence that efficiently conveys the core action, the target resource, sorting behavior, and pagination behavior. There is no redundant or filler content.

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, read-only listing tool with comprehensive parameter documentation and clear annotations, the description is complete. It covers the essential behavior an agent needs: what is listed, the ordering, and how pagination is handled.

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 input schema provides complete 100% description coverage for all parameters, including cursor semantics, filter, orderby, maxItems, and sectionGroupId. The description does not need to repeat parameter details, and it adds only general pagination context beyond the schema.

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 sections inside a OneNote section group.' This clearly differentiates it from sibling tools like list-onenote-notebook-sections or list-onenote-section-pages, which operate on different scopes.

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 communicates the context of use: listing sections within a section group. It does not explicitly name alternatives or exclusions, but the tool name and scope make the intended usage unambiguous relative to the many OneNote sibling tools.

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