managebac_get_class_grades

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

With no annotations, the description must disclose behavioral traits but only says 'Get grade/score-like items.' It does not mention whether the operation is read-only, what happens if the class is not found, or any other behavioral aspects like return format or pagination.

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 with no wasted words. However, the phrasing 'grade/score-like items' is imprecise, suggesting room for improvement while still being efficient.

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 4 optional parameters, no output schema, and multiple similar sibling tools, the description is overly terse. It lacks information about return values, how to choose a class identifier, and how this tool differs from managebac_get_grades or managebac_get_recent_class_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?

Schema coverage is 100% with detailed parameter descriptions (e.g., path, classId, maxItems, className). The tool description adds no additional meaning beyond what is already in the schema, earning the baseline score of 3.

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 'Get grade/score-like items for one ManageBac class/course.' It identifies the verb and resource, but 'grade/score-like items' is vague and does not differentiate from siblings like managebac_get_grades, managebac_get_recent_class_grades, or managebac_get_class_gpa.

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 such as managebac_get_recent_class_grades or managebac_get_grades. There is no mention of prerequisites, exclusions, or typical use cases.

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