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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety is covered. The description adds the meaningful behavioral fact that this shelf takes no query and returns the default curated set, but says nothing about pagination, shelf size, or how results differ from spotlight/charts, which is the information an agent actually needs.

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 tight sentence with the identifying information ('default', 'query-less', 'recommendation shelf') front-loaded and no filler. It is arguably over-compressed, but every word earns its place.

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?

An output schema exists, so return values need no explanation, and annotations cover the read-only profile. The remaining gap is routing: with thirteen microsoftstore_* siblings, the description does not say when to pick this shelf over spotlight, charts, or editorial, leaving selection ambiguous.

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 both parameters (Locale, Country) documented as BCP-47 and ISO-2 with defaults, so the schema carries the semantics. The description correctly adds that there is no query parameter, which explains why only these two localization knobs exist.

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 concrete verb-like resource ('recommendation shelf') and adds the distinguishing modifier 'query-less' plus 'default', which separates it from microsoftstore_search. It stops short of naming the sibling tools it most overlaps with (spotlight, charts, editorial), so differentiation is implied rather than explicit.

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 phrase 'query-less' implies the usage condition (no search term available, want the default shelf), which nudges the agent away from microsoftstore_search. However, no alternative is named and there is no explicit when-not guidance against the many other browse shelves (spotlight, charts, editorial, categories).

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