edubase_get_quiz_grading_preset

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, aligning with the 'Get' action. The description adds that thresholds and grades are included, which is content rather than behavior. It does not disclose additional behavioral context such as error conditions or permissions.

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, front-loaded sentence with no wasted words. It conveys the action and key result detail efficiently.

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?

Combined with the annotated schema (read-only, idempotent, single fully-described parameter) and the available output schema, the description provides sufficient information for correct invocation. It does not explicitly mention when to choose the list variant, but that gap is minor for a single-resource getter.

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?

With 100% schema description coverage, the schema already documents the sole parameter 'preset' as an identification string. The description does not elaborate on how to format or interpret this parameter, so it adds no extra semantic value beyond the baseline.

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 states a specific verb (Get), a clear resource (grading preset), and highlights that it returns thresholds and grades. This clearly differentiates it from the plural 'get_quiz_grading_presets' list operation and other preset mutation tools.

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 singular 'a grading preset' implies retrieving one preset by identifier, but the description offers no explicit guidance on when to use this versus alternatives like get_quiz_grading_presets or the post/patch/delete operations. No exclusions or selection criteria are provided.

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