search_campus_restaurants

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

With no annotations, the description carries the full burden. It discloses that the tool sets Grubhub locationMode=CAMPUS, which is a key behavior. However, it does not mention authentication requirements, error handling, or rate limits.

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 with two introductory lines and a clear parameter list. It is front-loaded with purpose and usage context.

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 search tool with an output schema, the description covers purpose, usage, and parameters adequately. However, it omits details such as authentication requirements and what happens with no results.

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 description adds explanations for all 5 parameters beyond the empty schema, including context for latitude/longitude and default values for page_size/page_num. However, the explanations are minimal and do not provide additional constraints or examples.

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 searches Grubhub campus/onsite restaurants near a campus location, specifies it is for campus-card dining, and distinguishes from the sibling tool search_restaurants by noting it sets locationMode=CAMPUS.

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 says 'use this for campus-card dining', providing clear context for when to use. However, it does not explicitly state when not to use or mention alternatives beyond the implied sibling.

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