get_assignment_analytics

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

Annotations declare readOnlyHint=true, indicating a safe read operation. The description adds 'detailed analytics' but does not elaborate on what data is returned (e.g., scores, statistics). While not contradictory, it offers minimal behavioral insight beyond the annotation.

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 concise with a single opening sentence and an args list. The main purpose is front-loaded. The args list is somewhat redundant with the schema but remains clear and brief.

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?

The tool is simple (two required parameters), has an output schema to document return values, and annotations indicate read-only. The description, while sparse, is sufficient for a straightforward read operation given the supporting structured information.

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 schema has 0% description coverage; the description provides brief explanations for each parameter (e.g., 'course_identifier: Course code or Canvas ID'). This adds some value but is minimal, leaving ambiguity about exact formats or allowed values.

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 retrieves analytics on student performance for a specific assignment. However, among siblings like 'get_assignment_details' and 'get_student_analytics', it does not differentiate the type or scope of analytics provided.

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 explicit guidance on when to use this tool versus alternatives. The description does not mention prerequisites, context, or when to avoid using it. Sibling tools exist but no comparisons are made.

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