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

Annotations already declare readOnlyHint and non-destructive behavior, so the description only needs to add context beyond that. It adds that orders are scoped to the authenticated user's students and limited to 'recent,' which is useful. However, it does not define 'recent' or disclose ordering/pagination, so the added behavioral context is moderate.

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 short and front-loaded with the core purpose. Minor redundancy exists because 'Read-only' restates an annotation, but it is still economical and easy to parse.

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 simple read-only tool with one optional parameter and an output schema, the description provides enough to invoke it correctly. The only notable gap is the undefined meaning of 'recent,' but that is not likely to prevent correct usage given the output schema and annotations.

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 schema already covers student_id with 100% description coverage, including the constraint that it must be the user's own student. The tool description merely restates 'Optionally filter by student_id' without adding any new meaning, so the baseline 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 and resource: it returns recent lunch orders for the authenticated user's students. It also distinguishes itself from siblings like get_monthly_orders (recent vs. monthly) and order_lunch (returns vs. creates), so the agent can tell it apart.

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 gives clear context: it is for reading recent lunch orders and optionally filtering by a student. It does not explicitly mention when not to use it or name alternatives such as get_monthly_orders for a broader history, so it stops short of full routing guidance.

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