Get Assignment Analytics

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the read-only nature is established. The description adds valuable behavioral context by detailing what the tool returns (min, max, median, quartiles, submission count, tardiness breakdown), going beyond the structured annotations.

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 two concise sentences. The first establishes the core purpose and output, the second explains the optional parameter behavior. Every sentence earns its place with no redundancy.

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?

Given there is no output schema, the description carries the burden of explaining return values and does so thoroughly: statistical summary fields, submission count, tardiness breakdown with categories. It also covers parameter scoping and reads as complete for the tool's complexity, supplemented by annotations.

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 the schema already fully documents both parameters. The description's guidance on assignment_id essentially mirrors the schema's own description ('Scope the result to a single assignment ID. Omit to return analytics for all assignments'), adding no new semantic information.

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 tool's function: 'Get score distribution analytics for assignments in a course.' It lists specific outputs (statistical summary, submission count, tardiness breakdown) and distinguishes itself from sibling tools like get_course_analytics and get_student_analytics by focusing on assignment-level score distribution.

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 provides clear context on when to use the tool (for assignment score analytics) and how to scope it to a specific assignment via assignment_id, with an explicit 'omit to return analytics for all assignments.' However, it does not name alternative tools or state exclusions, so it misses the explicit 'when-not-to-use' guidance.

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