list_students

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

With no annotations, the description carries full burden. It discloses that it returns the full roster in one call, implies read-only behavior, and lists the output fields. It also tells the agent how to leverage the returned id, which is useful behavioral context not captured in 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 concise and front-loaded: it states the purpose first, then the output fields, then the usage note, then the parameter list. Every sentence earns its place with no redundant fluff.

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 with three parameters and a clear output specification, the description is largely complete. It covers the return format and how to use the output. It doesn't mention pagination, ordering, or volume limits, but these are not critical for this tool's expected use.

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 0%, so the description must fully explain parameters. It does so: school_id is sourced from list_schools, grade is a case-insensitive filter with an example, and name_contains is a case-insensitive substring filter. This adds meaning beyond the bare schema types.

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 lists students on a school's admin roster and specifies the returned fields (id, name, grade, SIS id, guardians). This distinguishes it from class-specific listing tools like list_class_students, even though it doesn't name them.

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?

It gives context on how to use the result IDs (as student_id in related tools) and explains the optional filters, but it does not explicitly state when to use this tool over alternatives like list_class_students or list_grades. No exclusions or alternative routes are mentioned.

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