taco_bell_app_menu

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

With no annotations provided, the description carries the full burden of disclosing behavior, and it does so well: it explains the unusual backend, that no cookie/session/account is needed, that combat responses are fully resolved with choices and defaults, and that dayparts are included. It does not cover error cases or response size, but the major behavioral expectations are clear.

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 main purpose is front-loaded in the first sentence, with supporting details layered afterward. It is somewhat wordy and repeats 'full/complete' and 'one restaurant', but every detail adds meaningful context about combos, dayparts, and auth requirements.

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 single-parameter tool with no output schema, the description provides enough context: what data is returned, how combos are structured, what dayparts are, and where the input value comes from. A more explicit statement of the response shape would be ideal, but the description is sufficient for correct invocation.

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 input schema already documents store_number fully and points to /taco-bell/stores, giving 100% schema coverage. The description repeats that source but adds little beyond it, so the baseline score of 3 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 verb and resource: get one Taco Bell restaurant's full app-ordering catalog, including combos. It also differentiates from siblings by noting this is the only endpoint in the family that publishes combos, and it specifies the required store-number input.

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 strong contextual guidance: it identifies the tool as the unique source for combos, notes that it uses a separate credential-free backend, and directs the agent to GET /taco-bell/stores for store numbers. It does not explicitly name alternatives or state 'use X instead', but the uniqueness claim makes the use case clear.

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