autocomplete_search

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

No annotations are provided, so the description carries full responsibility for behavioral disclosure. It only describes inputs and does not mention rate limits, result behavior, side effects, or whether it is read-only. For a tool with no annotations, this is insufficient.

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 and front-loaded with the purpose. It uses a clear arg list format. It earns its sentences but could include more detail without increasing length significantly.

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 the tool has 4 parameters and an output schema exists (context signal), the description does not need to explain return values. However, it lacks important context such as constraints on coordinates, maximum query length, or the fact that latitude/longitude are required. The description minimally covers completeness, but gaps remain.

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 description coverage is 0%, so the description must compensate. It adds minimal meaning: 'query' is described as 'partial search text,' latitude/longitude as 'for location context,' and location_mode has a default. However, it provides no additional constraints, formats, or examples, and repeats schema information without significant enrichment.

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 'get autocomplete suggestions for a search query,' identifying the specific verb and resource. This distinguishes it from sibling tools like search_restaurants and search_campus_restaurants, which perform full searches rather than autocomplete.

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 lists arguments and implies usage for partial search queries, but it does not provide explicit guidance on when to use this tool versus alternatives (e.g., full search tools). There is no mention of when not to use it or prerequisites.

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