canvas_bulk_grade

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

With no annotations, the description carries the full burden and does so well: it discloses the mutation ('MUTATES STUDENT RECORDS'), the asynchronous processing model, that it returns a Progress object with delayed visibility, and the absence of a partial-failure report. These are exactly the traits an agent cannot infer from the schema.

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?

Front-loaded with purpose, mutation warning, and async caveat before the args list. The consequence of the write is stated twice (the all-caps line and the 'highest-consequence call' paragraph), which is mild redundancy, but every section still carries information.

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?

Covers purpose, side effects, async timing, verification path, and all parameter formats for a 3-param bulk mutation. The output schema exists, and the description still usefully summarizes the Progress return, so nothing an agent needs is missing.

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 compensate and it does: it documents all three parameters, gives concrete grades_json examples including both the object and bare-string shorthand forms, and states the course_id default behavior.

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?

States a specific verb and resource with an explicit scope qualifier ('Post many grades to one assignment at once'), which immediately separates it from the single-grade sibling canvas_grade_submission. An agent can identify the tool without opening the schema.

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?

Gives a clear operational precondition ('show the instructor the complete table ... and get an explicit go-ahead; never assemble one from inference') and names the verification follow-up (canvas_list_submissions). It never states the when-NOT condition, e.g. that single grades should go through canvas_grade_submission, so it falls short of full alternative routing.

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