remove_rubric_from_assignment

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

No annotations are provided, so the description must carry the burden of behavior. It discloses the key side effect that the rubric is not deleted, but it does not mention other behavioral aspects such as permissions, error conditions, or idempotency. It is partially transparent but not fully sufficient.

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 sentence with no filler words. It is front-loaded with the action and ends with a clarifying constraint.

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 simple two-parameter tool with no output schema, the description adequately states the purpose and the critical non-destructive side effect. It lacks explicit usage exclusions or more detailed behavior, but it is sufficient for a basic operation.

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 input schema covers 100% of parameters with descriptions (course_id, assignment_id). The tool description does not add any new parameter semantics beyond the schema, so the baseline score of 3 applies.

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 uses a specific verb+resource: 'Remove a rubric association from a specific assignment' and explicitly clarifies that it does not delete the rubric itself. This distinguishes it from sibling tools like delete_rubric, which deletes the rubric.

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 when to use it: when you need to detach a rubric from an assignment while preserving the rubric. The phrase 'without deleting the rubric itself' contrasts with delete_rubric, but it does not explicitly name alternatives or provide exclusions, so it falls short of a perfect score.

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