moodle_get_overview_grades

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

The description adds no behavioral context beyond the annotations (readOnlyHint, idempotentHint, destructiveHint). It does not disclose return format, data scope, or any limitations. Since annotations already cover safety, the description's lack of additional context lowers its value to minimal.

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 concise sentence, front-loaded with the key action. It wastes no words, but it is so minimal that it borders on under-specification. Still, for the simplicity of the tool, it earns a high score.

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?

The description is adequate for a simple read-only tool but lacks any detail about return values or structure. With no output schema, the description should clarify what the 'overview' contains, but it only says 'total grades for all courses'. This leaves some ambiguity, making it a minimum viable description.

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 tool has zero parameters, so the baseline is 4 per the scoring rules. The description adds scope context ('all courses') but no parameter details are needed. The empty schema is fully covered.

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 clearly states the tool returns an overview of total grades for all courses, which is a specific read operation. It distinguishes from sibling tools like moodle_get_grades by emphasizing 'all courses' and 'total grades' rather than per-course details. However, it lacks an explicit verb like 'get' or 'list', making it slightly less direct.

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 description provides no guidance on when to use this tool versus alternatives. It does not mention that this is for a high-level summary or that more detailed grade information is available via moodle_get_grades. There is no usage context or exclusions.

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