Get My Grades

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

No annotations are provided, so the description carries full burden. It describes what data is returned (grade items with points, percentages, comments) but doesn't disclose behavioral aspects like authentication requirements, rate limits, error conditions, or whether this is a read-only operation. The description is accurate but lacks operational context.

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 sentences that are front-loaded with the core functionality, followed by specific usage guidance. Every word serves a purpose - no redundancy or unnecessary elaboration. The structure moves from what the tool does to when to use it efficiently.

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 single-parameter read operation with no output schema, the description provides good context about what data is returned and when to use the tool. However, without annotations or output schema, it could benefit from more behavioral transparency about authentication, error handling, or response format details.

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 documents the single parameter well. The description adds value by explaining the semantic behavior when the parameter is omitted ('If omitted, returns grades for all enrolled courses'), which complements the schema's technical specification.

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 action ('fetch your grade breakdown') and resource ('for a specific course or all enrolled courses'), with specific details about what's included ('grade items with points, percentages, and comments'). It distinguishes this from sibling tools like get_assignments or get_upcoming_due_dates by focusing exclusively on grades.

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?

Explicitly states when to use this tool: 'when the user asks about grades, scores, marks, GPA, academic performance, or how they're doing in a class.' This provides clear context for the agent to recognize relevant user queries and select this tool appropriately.

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