mhlb_get_order_form

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

The annotation readOnlyHint=true already signals a safe read operation. The description adds value by disclosing that the returned model is the exact structure expected by mhlb_create_order and is pre-populated with available items. This provides actionable behavioral context beyond the annotations, without contradicting them.

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?

A single, well-structured sentence that front-loads the core purpose and then clarifies the return value with a dash. There is zero redundancy; every word earns its place.

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?

Since there is no output schema, the description adequately explains the return value (blank order model pre-populated with available items) and its intended use. Combined with annotations covering safety and schema covering parameters, nothing essential is missing for an agent to call this 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?

Both parameters are fully documented in the schema (100% coverage) with references to source tools (mhlb_get_menu/mhlb_get_calendar for eventId, mhlb_list_students for studentId). The description itself adds no additional parameter semantics, so the baseline of 3 applies.

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 ('Get'), a specific resource ('blank order model'), and the context ('for a student on a specific lunch event'). It also explicitly connects to mhlb_create_order, which distinguishes it from mhlb_get_order and other siblings. The purpose is unambiguous.

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 implies this tool is used before creating an order by stating it provides the exact structure that mhlb_create_order expects. It names the create tool and describes the pre-populated items. However, it does not explicitly state when NOT to use it (e.g., for retrieving an existing order via mhlb_get_order), so the guidance is strong but not fully explicit.

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