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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the description does not need to state that this is a safe read operation. It adds no further behavioral details such as authentication or data freshness, but it also contradicts no annotations.

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 one compact sentence with a front-loaded summary ('Who the store is and how buying works') followed by a concise list of covered topics. Every phrase earns its place, and no redundant clauses appear.

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?

For a simple read-only lookup with one optional parameter and no output schema, the description adequately enumerates the returned content. A short usage-note distinguishing it from shipping/availability siblings would improve completeness, but nothing essential for invoking the tool is missing.

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?

The only parameter, lang, has 100% schema description coverage, so the description does not need to explain it. The description's mention of 'languages' refers to store information content rather than the parameter, but the schema removes ambiguity.

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 clearly identifies the resource—store-level information—and lists specific content areas: delivery countries, cost/time, payment methods, returns, currency, languages, and contact. It does not simply restate the title, and its store-wide scope helps distinguish it from product/search/shipping siblings, though it lacks an explicit verb.

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 enumerated topics imply when to call this tool: when the user needs delivery, payment, return, or contact information. However, it never explicitly contrasts with alternatives like get_shipping_quote or check_availability, so routing must be inferred from the field list rather than direct guidance.

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