create_grading_standard

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

Discloses sorting behavior, JSON key differences (grading_scheme_entry vs grading_scheme), and return value (id). Annotations indicate destructiveHint: true, which is slightly contradictory as creation is not destructive, but description does not mislead.

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?

Description is well-structured and informative but slightly verbose (6 sentences). Could be more concise by merging some details. Still earns its place overall.

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 creation context, parameter details, behavioral sorting, return id, and next step (apply_grading_standard_to_course). Complete for a tool with no output schema.

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?

With 100% schema coverage, baseline is 3. Description adds significant meaning: explains lower-bound integer-to-percentage conversion, fraction 0–1, sorting, and Canvas API body key, enhancing understanding beyond schema.

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?

Clearly states 'Create a new grading standard' with details on context (course or account) and distinguishes from sibling apply_grading_standard_to_course for activation.

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?

Explicitly specifies when to use (to create a grading standard), required context parameters (course_id or account_id), admin requirement for account, and directs to sibling tool for activation.

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