create_students

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

Goes well beyond annotations by disclosing batch semantics, email lowercasing, duplicate handling ('FIRST occurrence wins'), and the OAuth scope requirement. These are behavioral traits an agent cannot infer from the name, schema, or 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 the core purpose and batch nature, then parameter details, then behavior caveats, then the scope requirement. Every sentence adds distinct value and nothing is redundant.

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 single-parameter tool with an output schema present, this description covers purpose, parameters, edge-case duplicate behavior, the enrollment exclusion, and authentication scope. An agent has everything needed to select and 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?

Schema coverage is 0% and the students array items have no documented properties, yet the description fully compensates: it explains that each item needs an 'email' (required, lowercased), and that 'first_name' and 'last_name' are optional with a 50-char limit. This is exactly the meaning the schema is missing.

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 ('Register') and resource ('learners'), immediately clarifies it is a BATCH operation, and distinguishes its scope from enrollment by saying it does not enroll anyone. This is more than enough to tell it apart from siblings like bulk_enroll_students or update_students.

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?

Explicitly tells the agent when this tool is NOT the right choice: 'Registering an account does not enrol anyone in anything - use bulk_enroll_students for that.' It also implies creation-only use and provides a named alternative, giving clear routing guidance.

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