search_public_stores

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

With no annotations, the description carries the full behavioral burden. 'Verified' and 'public' usefully signal that results are limited to vetted, publicly listed entities, but there is nothing about result caps/limit behavior, ordering, pagination, or what a match record contains for a read tool with a default limit of 15.

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 the verb and resource first and zero filler. It is efficient but too thin to be exemplary given the unresolved sibling overlap.

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?

Three optional parameters, no annotations, and no output schema means the description must explain what comes back and how to narrow results; it explains neither. The undefined boundary with search_public_catalog and get_public_store_details is the most consequential omission.

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 coverage is 67%: query and country are documented in the schema, only limit is bare. The description's 'by name, keyword, country, or city' largely restates the query/country field descriptions and adds no syntax, matching, or limit-cap semantics. Baseline 3 fits.

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 (searches) and resource (verified public E-Shop stores and companies) plus the searchable facets (name, keyword, country, city). It does not, however, distinguish itself from the sibling search_public_catalog or explain how it relates to get_public_store_details.

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 on when to use this versus search_public_catalog (which reads as an almost identical search entry point) or when to follow up with get_public_store_details. The only implied usage is 'you want to find stores', which the name already conveys.

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