list_class_students

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

No annotations are provided, so the description carries the full burden. It discloses that the tool lists students for a single class, but doesn't mention whether it returns full student objects or just IDs, whether it includes inactive/withdrawn students, or any pagination/ordering behavior. For a read-only list tool, this is a moderate gap.

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: one sentence plus an Args note. It front-loads the purpose and gives the key parameter hint. No wasted words, though the Args section partially duplicates the schema.

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 has an output schema, so return values are covered elsewhere. The description covers the essential input (section_id) and its source. It doesn't mention edge cases like empty classes or error conditions, but for a simple list-by-ID tool this is acceptable. The lack of behavioral details (e.g., whether it returns only active students) is the main gap.

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 0%, so the description must compensate. It does explain that section_id is a 'Class/section ID (from list_classes)', which adds provenance and meaning beyond the bare schema. However, it doesn't specify the expected format (integer is in schema) or any constraints beyond that. The single parameter is adequately explained for basic use.

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: 'List the students enrolled in one class.' This clearly distinguishes it from sibling tools like list_students (all students) and add_class_students (mutating enrollment). It doesn't explicitly name a sibling alternative, but the scope is clear enough.

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: call it with a section_id to get students in that class. It doesn't explicitly state when to use this over list_students or get_class, but the 'one class' scoping and the Args note provide adequate context. No exclusions or alternatives are named.

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