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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered by structured data. The description adds content-level context (help links, agent purchase scope) but says nothing about freshness, localization, or whether the policy content is authoritative or cached.

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 compact sentence with no filler, and the primary payload ('official store information') is front-loaded before the secondary items. The trade-off is that its brevity shades into vagueness on the agent-purchase clause.

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?

Complexity is minimal (no params, output schema present) so return values need no explanation, and the description covers the tool's surface areas. However, the 'alcance de la compra mediante agentes' component is a substantive capability left unexplained — an agent cannot tell whether it means eligibility rules, spending limits, or permitted actions.

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 tool takes zero parameters, so there is nothing for the description to disambiguate; baseline 4 applies. No parameter meaning is missing because the input schema is empty.

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 names a specific resource ('Información oficial de la tienda') plus two additional content areas (help links, agent purchase scope), which clearly separates it from product/cart siblings like get_product or quote_cart. It is a noun phrase rather than a verb+resource statement, and 'alcance de la compra mediante agentes' is fuzzy about what is actually returned.

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 explicit when-to-use or when-not-to-use guidance is given, and no sibling tool is named as an alternative. Usage is only implied: an agent can infer this is the place to check store policy and agent-purchase scope, plausibly before prepare_checkout, but that routing must be guessed rather than read.

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