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

Annotations already declare readOnlyHint=true, so safety is covered. The description adds value beyond that by naming the concrete data returned (name, domain, currency, timezone, account settings) and mapping to the underlying endpoint (Recharge REST: GET /store), which tells the agent what it actually receives.

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 front-loaded sentence plus a short endpoint reference; every clause earns its place by naming the resource and its return contents. No filler or redundancy.

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 usefully enumerates the returned fields so the agent knows what comes back. For a simple singleton getter this is nearly complete, though it could note that no arguments are required or that it reflects a single account-level store.

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 to document; the baseline for a no-arg tool is 4. The schema is trivially complete and the description correctly implies a singleton, unparameterized call.

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 (Get) and resource (store/shop info) and enumerates the returned fields (name, domain, currency, timezone, account settings). This clearly distinguishes it from the charge/customer/order/subscription siblings, which all operate on different resources.

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 description implies usage context (retrieve account-level store configuration) but gives no explicit when-to-use or when-not guidance. Since this is the only store-retrieval tool among the siblings and takes no arguments, there are no alternatives to disambiguate against, so the implied usage is largely sufficient.

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