Get Unposted Grades

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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the 'Read-only' line adds little; however, 'usually empty for students' and the enrollment-visibility caveat are real behavioral expectations not present in structured fields. It doesn't describe the shape of returned entries, keeping it short of a 5.

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?

Three short sentences with the capability first, safety next, and the alternative last. No filler, and the most decision-relevant information (usually empty, use get_all_grades otherwise) is front-loaded.

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?

Sufficient for a single-parameter, read-only lookup: it says what is retrieved, what is excluded, and expected emptiness. Without an output schema, it could say slightly more about what a returned score record looks like, but the agent can call it confidently.

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?

Only one parameter and schema coverage is 100%, with the schema itself explaining the numeric course ID and pointing to list_courses. The description adds nothing about course_id, which is acceptable at this coverage level but is a baseline 3.

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 (get) and a precisely scoped resource (scores entered but not released, visible to the caller's enrollment). It is clearly distinguishable from get_all_grades, which it names explicitly.

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 routes the agent: use this for unreleased scores, use get_all_grades for released grades, and warns that the result is usually empty for students. The condition selecting this tool versus its main alternative is unambiguous.

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