mhlb_new_student_form

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

The annotations already mark the tool as readOnly, and the description's 'Get' wording is consistent with that. The description adds useful context by naming the contents of the response (blank profile plus dropdown options), but it does not go deeper into response shape, potential variability, or any other operational behavior. This is acceptable given the simple read-only nature, but not exceptionally transparent.

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 a single, focused sentence that front-loads the core action and result, then adds the downstream usage ('pass to mhlb_create_student'). No filler or redundant restatement of the tool name.

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 zero-parameter, read-only form-retrieval tool, the description is complete: it says what the tool returns, that the result is blank/ready to fill, and how it should be consumed. Without an output schema, it still gives enough context for an agent to invoke the tool confidently and chain it 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?

The input schema is empty, so there are no parameter semantics to document. Per the baseline for zero-parameter tools, the description does not need to add parameter-level detail, and it does not omit anything relevant.

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 action ('Get') and a specific resource ('blank student profile plus school/grade/teacher dropdown options'), and further clarifies the purpose by linking it to mhlb_create_student. The word 'blank' and the create-student linkage distinguish this tool from the sibling mhlb_get_student_form without needing to open any schema.

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 clearly implies when to use this tool: when preparing to create a new student, retrieve the blank profile and dropdown options, then pass the result to mhlb_create_student. It does not explicitly rule out alternatives like mhlb_get_student_form, but the blank/new orientation provides sufficient context.

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