managebac_get_classes

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

With no annotations, the description carries full burden for behavioral disclosure. It only states the tool 'gets' the list, but does not specify whether an active session is required, if data is cached, or what the output format is. For a read operation without annotations, more detail on side effects or constraints is needed.

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 sentence that conveys the essential purpose without any extraneous words. It is front-loaded with the verb and resource, making it efficient and easy to parse.

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?

Given no parameters and no output schema, the description is minimal. It provides the core purpose but lacks details about the return structure or how to interpret the output. For a straightforward list tool, this might suffice, but additional context about the data returned (e.g., class names, IDs) would improve completeness.

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?

There are zero parameters, and the description adds meaning by specifying the scope (visible to the logged-in student). Since the schema coverage is 100% (vacuously), the description adds value beyond the schema by clarifying the contextual filter, earning a 4.

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 explicitly states it retrieves the ManageBac class/course list for the logged-in student. The verb 'Get' with the specific resource 'ManageBac class/course list visible to the logged-in student' clearly defines the tool's action and scope, distinguishing it from sibling tools that focus on deadlines, grades, or session management.

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?

No guidance is provided on when to use this tool versus alternatives like managebac_get_class_grades or managebac_get_class_deadlines. There is no mention of prerequisites (e.g., requiring an active session) or context where this tool is appropriate. The sibling tools are diverse, but the description does not help the agent decide which to invoke.

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