willys_search_suggestions

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only states that the tool provides suggestions, but does not mention whether the operation is read-only, what the response format looks like, or whether a sessionId is required for authentication. The agent is left without crucial safety and behavior information.

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, concise sentence with no extraneous words. It is front-loaded with the core purpose and is appropriately sized for the tool's simplicity.

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?

The tool has no output schema and no annotations, and the description is too sparse. It does not specify what the suggestions look like, how the response is structured, or why sessionId is required. An agent would struggle to know what to expect from invoking the tool and whether any prerequisites exist.

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 mentions 'term' in a general sense, indicating that it is the search term, but it does not explicitly map the parameter name 'term' or explain its format. More importantly, the 'sessionId' parameter is completely unexplained. With 0% schema description coverage, the description fails to compensate for the lack of parameter 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 that the tool provides search suggestions (autocomplete) for a term. This distinguishes it from sibling tools like willys_search, which likely performs a full search, and willys_get_product_detail, which returns product details. The purpose is specific and unambiguous.

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 intended usage is implied by the phrase 'autocomplete for a term' – it is meant for scenarios like search-as-you-type. However, there is no explicit guidance on when to use this tool versus alternatives, nor any exclusions or conditions. The tool name and description suggest the use case, but the description does not articulate it clearly.

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