get_grades

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

The annotations already declare readOnlyHint=true, so the description does not need to repeat that. It adds useful behavioral context beyond the annotation: the result reflects the Canvas user-facing view and hidden grades remain hidden. This is meaningful additional transparency.

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, tightly-worded sentence with no filler. It front-loads the core purpose and adds the most important caveat about hidden grades in a compact clause.

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 low-complexity read-only tool, the description covers the output content and the hidden-grade behavior. However, the ambiguous optional course parameter and lack of any usage direction leave an important gap for an agent deciding how to invoke the tool correctly.

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 schema has 0% description coverage for the single optional 'course' parameter, and the description does not compensate. It never explains how to specify a course (ID? name?), what null means, or whether the parameter filters results to one course or returns all courses.

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 clearly identifies the resource (grades) and the scope (course totals and per-assignment scores), and adds a distinctive behavioral nuance ('as Canvas shows them to you'). It does not use an explicit verb, but the tool name supplies that, and the domain is clearly separated from siblings like announcements, tasks, and lectures.

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 implies this is the tool to use when you need grades as the student sees them, including the hidden-grade caveat. However, it gives no explicit guidance about when to use it over alternatives, what the optional 'course' parameter means, or what happens when it is omitted.

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