chipotle_restaurant

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

No annotations are provided, so the description bears full responsibility. It discloses the key behavioral trait: the returned record may lack hours and capability flags because there is no embeds parameter, which is critical for the agent to set expectations. However, it does not describe the full structure of the record or any error conditions, but for a simple read it's adequate.

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, uses exactly three sentences, and front-loads the primary purpose first. Every sentence adds value—no fluff. It efficiently explains the leaner nature and directs to a sibling when needed.

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?

With one parameter fully documented in the schema, no output schema needed (since it's just returning a restaurant record), and no nested objects, the description covers everything an agent needs: the input, the caveat about missing fields, and the alternative for richer data. Nothing critical is missing.

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 describes the parameter as 'Chipotle's numeric restaurant id' with 100% coverage, so the schema already carries the meaning. The description reinforces that it's a numeric identifier and how it's used, adding the context of the route's 'numeric restaurant number' terminology, making it unambiguous.

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 it fetches a single Chipotle restaurant by numeric restaurant number, distinguishing it from the sibling chipotle_restaurants and chipotle_restaurant_menu tools. The verb 'Get' and specific resource make the purpose unmistakable.

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?

Explicitly states when to use this tool versus the alternative: if the full record with embeds is needed, use /chipotle/restaurants with a tight radius. Provides clear context that this is a leaner route, guiding the agent on when to choose this or the sibling.

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