read_chapter_quiz_grading

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

With no annotations, the description carries the full burden and does correctly disclose the key trait: it is side-effect free with respect to selecting, submitting and retrying. It does not say what happens when no grading exists yet, whether prior submission is a precondition, or what the read returns (though an output schema covers the latter).

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 the verb and resource first and the negative scope second. Nothing is redundant or padded.

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 parameterless read tool with an output schema, the description supplies the essential behavioral guarantee (read-only, no submission or retry). Only the precondition question — whether grading must already exist and what is returned if it does not — is left open.

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 takes zero parameters, so there is nothing for the description to disambiguate; baseline 4 applies. The description corroborates that no selection or submission inputs are involved.

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 verb (read) and resource (existing platform grading) and clarifies the scope as observation-only, which separates it from submit_chapter_quiz, validate_reviewed_chapter_quiz and observe_chapter_quiz. 'Platform grading' is slightly loose compared to the tool name's 'chapter quiz grading', but the intent is unmistakable.

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 clause 'without selecting, submitting or retrying' rules out the mutating siblings, implying this is the tool for inspecting results after the fact. However, no alternative is named and no trigger condition is given (e.g. 'use after a submission to retrieve the resulting grade'), leaving the agent to infer when to pick this over observe_chapter_quiz.

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