list_students

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint, but the description adds substantial behavioral context: one-page pagination behavior, exact versus partial matching, inactive filter semantics, exposure of real names and emails, and the required OAuth scope. This goes well beyond the structured 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?

The description is line-broken into logical segments, front-loads the critical pagination warning, and every sentence earns its place. There is no filler or repetition, and the structure helps an agent parse the most important behavioral rules quickly.

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?

Given the tool's complexity and the presence of an output schema, the description covers all essential operational aspects: pagination contract, exact-match filter behavior, inactive filtering, PII sensitivity, and authentication scope. Nothing critical is missing for an agent to invoke the tool correctly.

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?

With 0% schema description coverage, the description compensates meaningfully for key parameters: filter_email is documented as exact and case-insensitive, filter_is_inactive is explained with the 'omit for both' rule, and next_cursor is mentioned in pagination context. Other parameters like page_size, page_cursor, and name filters rely on their self-explanatory names, leaving a minor gap.

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 states a specific verb and resource: 'Find learners registered with this organization.' It clearly conveys the tool's scope without ambiguity. However, it does not explicitly differentiate itself from siblings like find_learner or get_student, leaving some differentiation to inference.

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 strong usage guidance: it warns about pagination (check has_more, use next_cursor), explains exact-match semantics for filter_email, and tells how to handle filter_is_inactive. It does not name alternative tools or explicitly state when not to use this tool, which prevents a 5.

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