search_suggestions

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

The annotations include readOnlyHint=true, which already establishes that this is a safe read operation. The description adds no further behavioral context, such as result format, sorting, pagination, or scope of suggestions. It essentially restates the tool's name, providing minimal value beyond the structured annotation.

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 a single, focused sentence that front-loads the core purpose. It is appropriately sized for a simple tool and contains no extraneous words.

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?

Although an output schema exists, the tool has three parameters with no descriptions in the schema or the tool description. The sparse description does not adequately support correct invocation, particularly for the optional parameters entity_names and max_suggestions. The tool is simple, so the minimal guidance falls short.

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 has 0% description coverage, and the tool description does not explain any parameters. 'Partially typed queries' only implicitly references query_prefix, leaving entity_names and max_suggestions without any semantic guidance. The description fails to compensate for the absence of schema documentation.

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's function: 'Return autocomplete suggestions for partially typed queries.' This specifies the verb (return) and resource (autocomplete suggestions), distinguishing it from the many data-lookup siblings. However, it does not explicitly contrast it with search_entities, so it is clear but not maximally differentiated.

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 guidance is provided on when to use this tool versus alternatives like search_entities or search_facets. The only usage hint is 'partially typed queries,' which implies an autocomplete scenario, but there are no explicit context, exclusions, or alternative references.

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