Get Grades And Notebooks

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

With no annotations, the description carries the full behavioral burden, yet it does not say whether authentication/session cookies are required (relevant given the set_session_cookies and check_auth_status siblings), whether results span all enrolled courses or only the current term, or whether the returned set is bounded. The parenthetical domain term 'poznámkové bloky' is the only added context, and return values are covered by the output schema.

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?

One front-loaded sentence with no filler, leading with the verb and the returned resource set. The untranslated Czech term in parentheses is minor domain clarification rather than wasted text.

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?

This is a simple one-optional-parameter read tool with a full output schema, so return-value documentation is not needed. What remains missing is only peripheral: authentication expectations and how to choose this tool over its siblings.

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 description coverage is 100% and the single optional course_code parameter is already documented in the schema with an example. The description adds no meaning about how the filter interacts with results (e.g. what is returned when omitted), so the baseline 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 ('Fetch') with a concrete set of resources: evaluation records, test points, homework scores, and grades from course evaluation notebooks. An agent can tell this is a grades/evaluation retrieval tool rather than an email, timetable, or course-catalogue tool, though it never names the nearest sibling (get_study_credit_summary, get_study_progress_check) to draw a hard boundary.

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?

There is no when-to-use or when-not-to-use guidance and no mention of alternatives among the 21 siblings. The agent must infer from the resource name alone whether this or get_study_credit_summary / get_study_progress_check is the right call for a given question.

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