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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds genuinely useful context by noting the endpoint is 'credential-free,' implying no authentication is required. It says nothing about rate limits, response size, or the shape of suggestions, so it adds only modest value beyond annotations.

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?

A single front-loaded sentence with zero filler. Every clause earns its place by naming the resource, the brand, and the auth-free nature of the endpoint.

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 read-only suggest tool with full parameter schema coverage, complete annotations, and an output schema, the description is nearly sufficient. The remaining gap is routing/usage guidance against the crowded set of sibling suggest and search tools.

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 100%, with q, limit (default 10, max 20) and types (allowed values and default) all documented in the schema. The description adds no parameter meaning beyond that, so the baseline 3 applies.

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?

States a specific verb ('Returns') and a clear resource ('commerce search suggestions') scoped to Everlane's predictive search endpoint. It is distinguishable from generic search siblings by naming the brand and the suggestion resource, though it does not explicitly contrast with everlane_search or everlane_products.

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 when-to-use guidance, no prerequisites, and no mention of the many sibling suggest/search tools (e.g., everlane_search, everlane_products) that an agent must choose between. The reader must infer that this is a typeahead/autocomplete tool.

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