needs_grading

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

With no annotations provided, the description carries the full burden of disclosing behavior. It only states a defining condition (submissions waiting to be graded) but fails to mention whether it is read-only, how filtering works, what the output contains, or any side effects. This is minimal behavioral transparency.

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 phrase, which is concise in length, but it is under-specified rather than efficiently informative. It omits critical details and does not earn its place as a useful explanation.

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 tool with two parameters, no annotations, and an output schema, the description provides almost no contextual completeness. It doesn't explain how the course parameter scopes the result, what 'only_open' affects, or what fields are returned. The description is inadequate for an agent to reliably select and invoke this tool.

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 input schema has 0% description coverage, and the tool description mentions neither the 'course' nor 'only_open' parameters. The agent receives no semantic help beyond the parameter names and types, which is insufficient for correct invocation.

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 'Assignments with submissions waiting to be graded' identifies a specific resource type but lacks a verb, so it doesn't clearly state what the tool does (e.g., list, fetch, filter). It is more than a tautology but not a crisp action statement, and it doesn't distinguish from sibling tools like list_submissions or classify_submissions.

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?

No guidance is provided about when to use this tool versus alternatives such as list_submissions or get_submission. There is no mention of context, prerequisites, or exclusions, leaving the agent to infer usage from the name alone.

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