list_users

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

With no annotations provided, the description carries the full burden. It discloses pagination behavior via offset/limit, explains role filtering, and notes the default limit of 50. It does not mention side effects or permissions, but for a list operation these are less critical, and the pagination/filter details add meaningful behavioral context 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 concise and well-structured: a clear opening statement, a usage sentence, and a bullet-like argument list. Every sentence earns its place, with no fluff or repetition.

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 is a simple listing operation with 4 parameters and an output schema. The description covers purpose, usage alternatives, parameter semantics, and pagination, making it complete for the tool's complexity. The presence of an output schema means return values need not be described in text.

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 is the sole source of parameter meaning. It explains each parameter: course_id (with how to find it), role (with allowed values and omission semantics), limit (with default), and offset (with paging usage). This fully compensates for the schema's lack of 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?

The description clearly states 'List enrolled users in a course' with a specific verb and resource. It also distinguishes itself from siblings by explicitly recommending get_enrollment_counts for headcounts and noting when to use this tool (when names or user IDs are needed).

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 provides explicit when-to-use guidance: 'Use get_enrollment_counts for a quick headcount' vs 'Use this when you need names or user IDs', and even suggests a downstream use case (before calling get_user_activity). It also mentions using list_courses to find course_id, which is a helpful cross-reference.

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