List Purdue dining locations

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

Without annotations, the description carries the full burden. It states the source is a live API and that the output includes open status and next meal period, which is moderately transparent. However, it does not disclose potential error conditions, rate limits, or output format details, leaving gaps for an agent.

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?

Two sentences, no wasted words. The first sentence immediately states the tool's purpose and scope, and the second adds the source and output details. Highly efficient 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?

Given no output schema, the description reasonably covers return values (open now, next meal period) and source. It could clarify the output structure (e.g., list of objects with fields) or mention that location names are included, but for a simple list tool it is mostly complete.

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%, so baseline is 3. The description adds value by enumerating the enum values (dining courts, Quick Bites, On-the-GO!) and linking the open_now parameter to 'whether it is open right now', reinforcing the schema descriptions and providing richer context.

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 'List', specifies the resource 'Purdue dining locations', and enumerates the categories (dining courts, quick bites, On-the-GO!). This distinctly sets it apart from sibling tools like dining_menu or dining_line_length by focusing on location listing rather than menus or wait times.

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 provides no guidance on when to use this tool versus alternatives. It does not mention related tools like dining_menu for menus or dining_line_length for wait times, nor does it state conditions like 'use when you need a list of all locations' versus 'use dining_menu for a specific location's menu'.

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