chipotle_get_location

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

No annotations provided. Description states 'get detailed information', implying read-only, but does not disclose authentication requirements, rate limits, or any side effects. For a read operation, minimal behavioral disclosure is acceptable but could be improved.

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?

Single sentence with no extraneous words. Concisely conveys the tool's purpose and input requirement.

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 lookup tool with one parameter and no output schema, the description covers the essential purpose and input. However, it lacks details about what 'detailed information' includes (e.g., address, hours, etc.), which would aid the agent.

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 one parameter. The parameter description adds value by specifying that the locationId comes from chipotle_search_locations results, providing context beyond the type definition.

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?

Description clearly states verb 'get', resource 'detailed information about a specific Chipotle location', and input method 'by its ID'. Distinguishes from sibling 'chipotle_search_locations' which searches rather than retrieves by ID.

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?

No explicit guidance on when to use versus alternatives like chipotle_search_locations or chipotle_select_location. However, the description implies it is for retrieving details after obtaining an ID, which is reasonable for a simple lookup.

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