list_students

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

No annotations are provided, so the description must carry the behavioral disclosure burden. It only mentions 'active students' and output fields, but does not state that the operation is read-only, how the 'course' parameter affects results, or any response characteristics beyond the schema.

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 extremely short and front-loaded, which is efficient, but it omits critical information. It is not properly sized for the tool's complexity, as it fails to address the required course parameter, making it under-specified rather than appropriately concise.

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?

While an output schema exists, the description lacks essential context about the required course parameter and when to use the tool. It is incomplete for a list operation that depends on a course filter, leaving the agent to guess at the tool's behavior.

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 lists a single required parameter 'course' with no description, and the description does not mention it at all. With 0% schema coverage and no compensation in the description, the agent cannot infer the parameter's format or purpose.

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 'Active students: id, name, email.' identifies the resource (students) and a scope (active), but lacks an explicit verb like 'list' or 'return'. It is clear enough that the tool deals with students, but does not fully specify the action, so it is not as strong as a purpose statement.

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?

There is no guidance on when to use this tool versus alternatives such as list_courses or get_course. It does not mention that a course is required or what filters apply, leaving the agent without direction on selecting this tool.

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