moodle_grades

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

Annotations already cover readOnlyHint and openWorldHint, so the safety profile is known. The description adds real behavioral value by disclosing the returned field set and the behavior shift when course_id is omitted (aggregate totals instead of per-course items).

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?

Two tight sentences, front-loading the primary behavior and then the fallback mode, with zero filler.

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 single-optional-param read tool with annotations covering safety and no output schema, the description supplies what an agent needs: the resource, the return fields, and the conditional behavior. Minor gaps (formatting/pagination) are not critical here.

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 coverage is 0% and the schema only labels the param 'Course Id'. The description meaningfully compensates by explaining that supplying course_id scopes results to one course and omitting it returns totals for all courses.

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 resource (grade items) and the fields returned (grade, max, %, weight, feedback), and distinguishes its two modes. Among the siblings, no other tool handles grades, so the resource specificity carries the differentiation.

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?

Clearly frames the two calling contexts: with course_id it returns one course's grade items, without it returns course totals across all courses. There are no alternatives named, but the conditional usage is explicit enough to guide the call.

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