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

Annotations already cover the safety profile (readOnlyHint=true, destructiveHint=false), so the bar is lower, and the description adds meaningful behavior: pagination limits ('Pages hold up to 100 students'), the cursor handoff mechanic, sort order, and an auth requirement ('Cotlet API key with access to this app'). These are useful operational details not present in the annotations.

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?

Front-loaded with scope and returns, then pagination, then the send_email cross-reference, then auth. Every sentence carries information, though the opening fragment ('Teachable: Students with name, email and join date, or...') is slightly awkward.

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?

There is no output schema, so the description correctly carries the return details (fields, ordering, page size) and the pagination contract. Combined with a documented, read-only, open-world tool this is nearly complete; only explicit exclusion criteria vs. other student-listing paths are missing.

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%, so baseline is 3, but the description adds real context: course_id selects the per-course enrollment view and cursor is explicitly tied to the prior call's next_cursor. It clarifies intent beyond the terse schema descriptions.

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?

States a specific verb and resource ('Lists students of your school, newest first') and adds the returned fields (name, email, join date), so an agent knows exactly what this produces. It also distinguishes the two scoping modes (whole school vs. one course), setting it apart from sibling course/lesson tools.

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?

Gives clear conditional guidance: 'Pass course_id to list only the students enrolled in one course', and routes to a related tool ('Use the emails with send_email when you need part of a course'). It stops short of naming a full alternative list tool or stating when NOT to use it, so it is clear context but not exhaustive.

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