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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true. The description's 'Read-only' repeats the annotation, but 'no signature' adds genuine auth context (no signing required) and the caller note explains view-dependence. Return/pagination behavior is not covered, so it stays at a 3.

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?

Two tight sentences: purpose first, then the read-only/auth note, then the optional-parameter caveat. No filler.

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 does the work of naming return contents (profile, products, services) and explaining the optional param. Complete enough to call correctly; only list pagination/ordering is unaddressed, a minor gap.

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 100%, so baseline is 3. The description goes beyond the schema by clarifying that `caller` is the account whose view to read (for caller-dependent results), which the schema's 'run the query as' only partially conveys. That added meaning earns the bump.

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 (View) and resource (a seller's public Marketplace store) and enumerates the content returned (seller profile, products and services). The word 'public' plus 'a seller's' distinguishes it from sibling tools like geode_market_view_my_seller_profile and the search_stores variants.

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?

Usage is implied by the name and the 'public store' framing — you call it to browse a specific seller's storefront. However, no alternative is named (e.g., search_stores_by_keyword for discovery vs. this for a known seller), and no when-not guidance is given.

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