Create Rubric

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

The description discloses the non-obvious optional behavior of immediately linking to an assignment employment. However, given destructiveHint=true and openWorldHint=true, it does not clarify whether creation can overwrite existing rubrics, what side effects linking has, or what the response is. The annotations already cover some safety profile, and the description adds only modest behavioral detail.

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?

Two short sentences, no fluff, front-loaded with the core purpose and the optional behavior. Every word earns its place.

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 create operation with nested objects and 4 parameters, the description gives the essential flow. But the openWorldHint and destructiveHint suggest unknown or destructive behaviors that are not elaborated, and there is no output schema to describe the return value. It is adequate but not rich.

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 has 100% parameter documentation, so the description need not repeat field meanings. It does add the semantic link between the optional association object and assignment linking, but mostly relies on the schema. Baseline 3 is appropriate.

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 states the action ('create') and the object ('rubric in a course'), giving a specific verb-resource pairing. It does not explicitly distinguish from sibling read tools like list_rubrics or get_rubric, but the creating vs. reading distinction is obvious.

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?

Mentions the optional assignment association, which is useful contextual guidance about a key feature. However, it gives no indication of when to use this tool relative to other sibling tools, nor any prerequisites (e.g., course_id must exist) or preconditions.

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