canvas_browse_course

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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, so the safety profile is covered. The description earns credit for genuine additions beyond that: lists return next_offset, limit is bounded 1..100, quiz reads are metadata only, and a failed section is never presented as an empty list (error-vs-empty semantics). It still says nothing about the refresh parameter's effect or caching behavior.

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 core capability and the section list are front-loaded, followed by pagination and caveat notes. Dense but each sentence carries operational information; only the confidence-signal sentence about failed sections could be tightened.

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 an output schema present and annotations covering safety, the description need not explain return shapes, and it correctly focuses on scoping, pagination and known failure modes. The remaining gap is the unaddressed relationship to sibling list/module tools and the unexplained refresh parameter.

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 0%, so the description must carry semantics, and it partially does: it names all section values and constrains limit to 1..100 while explaining that lists return next_offset for offset-based paging. It leaves 'refresh' and 'offset' entirely unexplained and does not describe course_id expectations, so the compensation is incomplete for a 5-parameter tool.

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 ('Browse a course section') and enumerates all nine sections the tool can return, so the agent knows exactly what is retrievable. It does not differentiate the tool from sibling list_* tools (list_modules, list_assignments, list_discussions, list_announcements) that overlap the same resources, leaving the relationship to inference.

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?

Usage is implied by the section enumeration, and there is one explicit conditional path: when files enumeration is forbidden, follow the modules alternative returned in that case. However, there is no guidance on when to choose this unified browser over the granular sibling listers, and no prerequisites or exclusions are stated.

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