list_students

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

With no annotations provided, the description carries the burden of disclosing behavior. It clarifies that this lists only students (not all roles) and includes specific enrollment data like section, activity, and last login. However, it does not mention pagination or any side effects, but for a read-only list tool this is a reasonable coverage level.

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 concise sentences: the first states the primary purpose and data scope, the second offers a clear alternative. No wasted words or redundant information.

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 simple list tool, the description is mostly complete. It explains the tool's purpose, what data is included, and when to use an alternative. It doesn't elaborate on filter semantics (already in schema) or return format (no output schema), but the description provides enough context for correct selection and invocation.

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% (all three parameters have descriptions), so the baseline is 3. The description adds no parameter-specific detail beyond what the schema already documents, so no additional value is provided.

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 uses a specific verb 'List' and clearly identifies the resource as 'students enrolled in a course' with a defined scope ('enrollment-specific data'). It explicitly distinguishes itself from the sibling tool by contrasting with 'list_users_in_course'.

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?

Directly states the alternative use case: 'For a simpler user list with any role (teachers, TAs, etc.), use list_users_in_course instead.' This gives clear when-to-use and when-not-to-use guidance, citing the sibling tool.

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