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

Annotations declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered. The description adds no behavioral context—no mention of what a 'shop profile' includes, whether it requires authentication, or any special constraints. With annotations present, the description could still add value, but it provides none beyond the title.

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 extremely short but not informative. It is not front-loaded with useful information; it is under-specified rather than concise. It fails to earn its place by conveying any actionable detail.

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 an output schema present, the description does not need to explain return values. However, for a retrieval tool with annotations and a simple schema, it still lacks basic context about what the tool returns (e.g., shop metadata) or how it differs from related tools. The description is too sparse to be complete.

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%: the single parameter 'handle' is fully documented in the schema with an example. The description adds no additional meaning about the parameter. A baseline 3 is appropriate when the schema does all the work and the description contributes nothing more.

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 'Shop.app shop profile.' essentially restates the tool name (shop_app_shop) without a clear verb. It vaguely indicates the resource (a shop profile on Shop.app) but does not say what the tool does—whether it retrieves, returns, or lists shop profile data. It is close to a tautology and does not distinguish it from sibling tools like shop_app_shop_products or shop_app_shop_reviews.

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 tool or what alternatives exist. With many sibling tools related to Shop.app shops (shop_app_shop_products, shop_app_shop_reviews, shop_app_shop_locations, etc.), the agent gets no help in selecting the right one.

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