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

readOnlyHint=true already tells the agent this is a safe read. The description adds useful scope context by characterizing the profile as 'public' and listing exactly which fields are returned, but it says nothing about error behavior for an unknown slug, rate limits, or whether closures/hours are timezone-qualified.

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 dense sentence that front-loads the verb and resource, then lists outputs. The field enumeration is long but each item is informative rather than filler, so it earns its length despite reading as a run-on list.

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?

With no output schema, the description correctly carries the burden of describing return values and does so well. However, it is silent on the sole input parameter and on failure modes, leaving real gaps for an agent that must decide when to call this versus find_shops.

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?

There is one required parameter and schema description coverage is 0%, so the description is the only place semantics could be supplied — and it never mentions shop_slug, its format, or where the value comes from. The name is self-explanatory, but the description does not compensate for the coverage gap.

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 (Retrieve) and resource (public shop profile) and enumerates the returned fields, so the agent knows exactly what it gets back. It does not, however, differentiate itself from the sibling find_shops or explain that this is the by-slug lookup path.

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 sibling alternatives (find_shops for discovery, get_catalog/search_catalog for menu data). The only hint at usage is the required slug parameter, which the description never discusses.

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