get_upcoming_menus

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

With no annotations, the description carries full burden. It describes the operation as read-only (getting menus) and lists return fields, but does not mention safety aspects (e.g., no side effects) or potential limitations like rate limiting or authentication requirements.

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 sentence with a clear list of return fields, making it efficient. However, it could be slightly more structured (e.g., bullet points) for faster parsing, but overall it is concise and front-loaded.

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 list tool with one parameter and no output schema, the description adequately covers purpose and return values. However, it lacks details on pagination, ordering, or how the week_offset aligns with delivery schedules, which could improve completeness.

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 100% with the week_offset parameter already described. The description adds context ('available recipes for your next deliveries') that clarifies the parameter's purpose beyond the schema, enhancing understanding.

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 the tool retrieves upcoming menu options from Blue Apron and lists specific return fields (recipe names, descriptions, cook times, difficulty, dietary info), which differentiates it from sibling tools like select_recipes or skip_week.

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 viewing menus before recipe selection, but lacks explicit guidance on when to use versus alternatives like get_account or get_delivery_schedule. No 'when not to use' or direct sibling comparisons are provided.

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