Get Rubric Assessment

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

Annotations already declare readOnlyHint=true and openWorldHint=true; the description adds no additional behavioral context such as what the assessment contains, whether it can be missing, or how it relates to rubric definitions. It merely restates the operation at the same level as the annotations.

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, front-loaded sentence that states the resource and the scoping identifiers without waste. It could have added one clarifying clause about the response, but as written it is concise and readable.

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?

With no output schema and only read-only annotations, the description fails to clarify what a rubric assessment actually contains (e.g., ratings, comments, criteria) or what happens if none exists. It is adequate for a simple fetch but leaves some ambiguity about the returned structure.

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 already provides 100% coverage for all three parameters (course_id, assignment_id, user_id). The description mentions a 'specific student submission' which aligns with user_id but adds no semantic detail beyond the 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?

The description uses a specific verb ('Get') and names a precise resource ('rubric assessment') scoped to 'a specific student submission on an assignment.' It distinguishes itself from related tools like get_rubric by implying the assessment is tied to a submission, though it doesn't explicitly contrast with siblings.

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?

No guidance is given about when to use this tool versus alternatives such as get_rubric or submission-related tools. The context of 'specific student submission' hints at a use case, but there is no explicit differentiation or selection criteria.

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