get_orders

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

Annotations already convey readOnlyHint=true and destructiveHint=false; the description adds 'Read-only' and scopes results to the authenticated user's students, which is useful context. However, it does not go beyond this to mention pagination, rate limits, or other behavioral traits, so it only modestly exceeds the annotation baseline.

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 concise and front-loaded with the core purpose, followed by the optional filter. The final 'Read-only' is redundant given the annotation, so it is slightly less efficient than it could be, but overall it is well-structured.

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?

The tool is simple with one optional parameter, an output schema, and annotations covering safety. The description covers the return content and scope, but it leaves the term 'recent' undefined and does not clarify how this tool relates to get_daily_orders/get_monthly_orders, which is a meaningful gap for an agent deciding among siblings.

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 description coverage is 100%, so the baseline is 3. The description only repeats the parameter name ('filter by student_id') without adding meaning beyond the schema's own description ('must be your own'), so it neither compensates for gaps nor adds extra clarity.

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 clearly states a specific verb and resource: 'Returns recent lunch orders for the authenticated user's students' and enumerates included fields (items, menu date, status, total). It is clear but does not explicitly differentiate from siblings like get_daily_orders or get_monthly_orders, so it misses the top score.

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 usage for recent orders and mentions an optional student_id filter, but it gives no explicit guidance on when to choose this tool over the sibling order-fetching tools. No exclusions or alternative names are provided, leaving the agent to infer the distinction.

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