get_student_summaries

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

No annotations are provided, so the description carries full burden. It discloses a critical behavioral trait: 'this endpoint returns LIFETIME data and does NOT support grading_period_id — the tardiness counts include all assignments since the course began, not just the current semester.' This goes beyond a basic description and warns about a common misuse.

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?

Three sentences, each earning its place: first states purpose, second gives sibling alternative, third explains the lifetime-data caveat and alternative approach. Front-loaded and concise with no filler.

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?

Despite no output schema, the description lists the returned data (page views, participations, tardiness breakdown) and important limitations (lifetime, no grading_period_id, per-semester workaround). This is complete for a simple analytics tool and covers the essential context an agent needs.

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 coverage is 100% with both 'course_id' and 'sort_column' having descriptions (including enum values). The description does not add much about these parameters beyond the schema, but it clarifies that grading_period_id is not accepted, which is useful context. Baseline 3 is appropriate.

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 per-student engagement analytics for a course: page views, participations, and tardiness breakdown (missing/late/on_time counts).' It uses a specific verb and resource, and the inclusion of 'For enrollment/roster data, use list_students instead' distinguishes it from a sibling tool.

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 names an alternative ('use list_students instead') and provides a when-to-use-other guidance for per-semester counts ('iterate course submissions with a grading_period_id filter'). It also explains the lifetime-data limitation, giving clear context for when this tool is appropriate.

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