Get My Assignment Analytics

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

The annotations already declare read-only, idempotent, open-world, and non-destructive behavior. The description adds a useful operational detail: it returns an error if course analytics are disabled at the school. It also summarizes returned data, though it does not discuss permissions or rate limits.

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 compact and front-loaded: it first states what the tool returns, then notes read-only behavior, then the error condition. Every clause adds useful information, and nothing is unnecessarily verbose.

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?

With one fully documented parameter, no output schema, and annotations covering safety traits, the description fills the remaining gap by explaining the return content and the analytics-disabled error case. An agent has enough information to decide whether to call it and what to expect.

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%, and the single course_id parameter is fully documented in the schema, including how to obtain it via list_courses. The description adds no parameter-level details beyond what the schema provides, which is appropriate for a one-parameter tool.

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 states a specific verb and resource: getting the user's score on each assignment alongside class median, min, max, and on-time submission status. This is clearly distinguishable from sibling analytics tools such as get_my_activity_analytics and get_grade_trend.

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 implies usage by saying it returns the user's assignment scores with class comparisons, and it notes the error condition when course analytics are disabled. However, it does not explicitly say when to use this tool versus alternatives such as get_score_statistics or get_my_activity_analytics.

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