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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds modest context: it returns static reference data with no inputs required, and the shortlinks are stated to work on the website, which is a real behavioral detail. It does not describe freshness, caching, or whether contact/opening-time data can be stale.

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 markedly overlong for a zero-parameter info tool, with a sprawling nested parenthetical listing product categories and a closing sentence ('The store sells to businesses and organisations') that merely restates 'selling wholesale to businesses' from the opening. The returned fields are also enumerated twice in different words. It is front-loaded in spirit but poorly structured.

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 input schema and no output schema, the description carries the full burden of explaining what comes back, and it does enumerate the returned fields and links. It is complete enough to call correctly and set expectations, though it spends words on marketing taxonomy instead of confirming the shape of the response.

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. The description correctly conveys that the call needs no arguments and returns a fixed set of store attributes.

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 returned: the store's profile, contact details, opening times, currency, product count, and links to terms/privacy/shipping/contact/about/route pages. It is distinguishable from siblings like product_details or search because it is about the seller, not the catalog. It loses a point because the core statement is buried in a long parenthetical rather than stated as a crisp verb+resource sentence.

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 line 'Show the shopper who sells and on which terms before ordering' implies a pre-purchase context, which is a useful timing hint. However, it names no alternatives and gives no explicit when-not guidance, so an agent must infer that this is the right tool for seller/terms questions rather than order or product questions.

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