Teacher gradebook

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered. The description usefully names the returned content (per-exam totals and student marks), but says nothing about result size, pagination, or how a gradebook with many students behaves under openWorld access.

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?

A single sentence with the return content front-loaded and the filter caveat trailing; nothing is wasted. It is arguably too tight, leaving no room for the behavioral detail an agent would want, but sizing itself is good.

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 2-optional-param, read-only tool with no output schema, the description does state what comes back (per-exam totals and student marks) plus the filter options, which is close to sufficient. The remaining gap is the absence of any guidance on default scope when both filters are omitted.

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%, so both filter parameters are already documented, making 3 the baseline. The description only echoes 'optionally filter by class_id or subject_id' without adding meaning such as how the two filters combine or whether omitting both returns all classes/subjects.

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 ('Get') and resource ('teacher gradebook') and clarifies the payload with 'per-exam totals and student marks', which is more than a restatement of the name. It does not, however, distinguish itself from siblings like ictexam_get_exam or ictexam_item_analysis, so an agent must infer the boundary.

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?

'Optionally filter by class_id or subject_id' gives a mild usage cue about scoping the result set. There is no explicit when-to-use, when-not-to-use, or named alternative among the five sibling exam/class/subject tools, so the routing decision is left to inference.

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