BARS points

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

Annotations already establish this as a safe, idempotent, open-world read (readOnlyHint=true, destructiveHint=false, idempotentHint=true), so the safety profile is covered. The description adds genuinely useful behavior beyond that: the upstream source (bars.itmo.ru), the scope limitation to the current semester, and the shape of the result (per-discipline totals plus per-checkpoint points with min/max). It does not mention auth requirements or behavior for unknown discipline names, which keeps 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?

One tightly built sentence: source and scope first, then the return breakdown via a colon list, then the optional filter. No filler and nothing buried.

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, the description carries the return-shape burden and does so adequately by naming totals, per-checkpoint points, and min/max. The remaining gap is minor: no statement about authorization or what is returned when the discipline filter matches nothing.

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 parameter already documents itself as a 'case-insensitive part of a discipline name'. The description's 'Optionally filter by discipline name' restates that without adding matching syntax or edge-case behavior, so the baseline 3 for schema-covered params 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 gives a specific verb+resource: fetching current-semester points from BARS, broken down as totals per discipline and per checkpoint (labs, tests, exam) with min/max. It is clearly a grades-adjacent tool but never explicitly distinguishes itself from the sibling itmo_get_grades / itmo_get_grade_details, so an agent must infer the split from the 'BARS' and 'checkpoint' framing.

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 only usage statement is 'Optionally filter by discipline name', which is parameter guidance rather than when-to-use guidance. There is no indication of when this should be preferred over itmo_get_grades or itmo_get_grade_details, no prerequisites, and no exclusions.

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