chipotle_get_favorites

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

With no annotations provided, the description carries the full burden for behavioral disclosure. It only notes the login requirement, omitting details about read-only behavior, rate limits, response structure, or any side effects. For a GET operation, more transparency about data freshness or pagination would be helpful.

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, well-formed sentence that conveys the core purpose and a key prerequisite. It is front-loaded with the action and resource, with no unnecessary words.

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?

Despite having no parameters, the tool is simple but lacks detail about what constitutes a 'favorite order' and the expected output format. With no output schema, the description should at least hint at the return structure (e.g., list of order IDs or items). This is minimal for an agent to fully understand the tool's output.

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 tool has zero parameters and schema coverage is 100%, so the schema inherently explains all inputs. The description adds no parameter-specific meaning, but this is acceptable given no parameters exist. Baseline 4 is appropriate.

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 saved favorite orders, specifying the verb 'Get' and the resource 'saved favorite orders from your Chipotle account'. This distinguishes it from related sibling tools like chipotle_get_order_history, which returns past orders, and chipotle_reorder, which reorders past items.

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 mentions a prerequisite ('Requires being logged in') but provides no guidance on when to use this tool versus alternatives like chipotle_get_order_history or chipotle_start_order. There is no mention of exclusions or context for optimal use.

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