ic_list_recent_grades

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

With readOnlyHint=true, the safety profile is already clear. The description adds useful behavior—server-side filtering by scoreModifiedDate and a 14-day default cutoff—without contradicting the annotation. It does not cover response shape or pagination, but the annotation lowers the burden.

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 tightly packed sentences that deliver purpose, filtering behavior, parameter format, and default value with zero waste. Every sentence contributes essential information.

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?

No output schema exists, so the description carries more responsibility for return-value expectations. It states the result is a list of recently-graded assignments, and the view parameter in the schema describes response shapes. Missing explicit pagination or alternative-tool guidance makes it adequate but not complete.

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 50%; view and since have rich schema descriptions, and the description further clarifies since's format and default. district and studentId have no schema descriptions but their names make them self-evident. The description partially compensates for the coverage gap.

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 verb 'List' and the resource 'recently-graded assignments for a student', which is specific enough to distinguish it from generic grade/assignment lists. The term 'recently-graded' and the scoreModifiedDate filter signal the tool's niche, though it does not explicitly name sibling 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 description explains how to set the since cutoff and its default, which is useful operational guidance. However, it does not explicitly state when to use this tool over ic_list_grades or ic_list_assignments, leaving the agent to infer the recency-based usage from the name and filter.

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