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

No annotations are supplied, so the description carries the full behavioral burden and discloses almost nothing: it does not say whether this performs a lookup, whether the content is static or live per-store configuration, whether any auth/context is required, or what a caller receives. Only the implied read-only framing can be inferred from the topic-list phrasing.

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?

It is a single short fragment with no filler, so nothing is wasted, but it is under-specified rather than concise: a leading verb and an object (e.g. 'Returns ProfitShop store details covering...') would cost two words and remove the ambiguity. Front-loading is fine since there is only one 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?

For a simple zero-argument lookup, the topic list gives an agent a reasonable sense of what topics the response covers. However, with no output schema and no annotations, the description should say what the call actually returns (a store-info object? a single string per topic?) and is silent on that.

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 and the schema is empty but open (additionalProperties: true), so there is nothing for the description to disambiguate. Per the zero-parameter baseline, no gap is held against it here.

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 is a noun-phrase topic list ("shipping, payment methods, returns, contact details") with no verb, so it only implies retrieval of ProfitShop store information rather than stating it. The subject areas are specific enough to guess the resource, and the 'store_info' name plus the sibling list (get_product, search_products) makes the broad domain clear, but an agent must infer the action.

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?

There is no statement of when to call this versus anything else, no prerequisites, and no exclusions. The sibling tools are product-oriented, so overlap is unlikely and the lack of routing guidance is less damaging, but nothing in the text helps an agent decide to use it.

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