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

With no annotations, the description carries the full burden. It usefully discloses scope ('live' listings only) and enumerates the returned fields, but says nothing about authentication requirements, behavior for non-live or unknown slugs, or rate limits on a read endpoint.

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 sentence with no waste, and the identifying mechanism (slug) is front-loaded before the payload list. Minor cost: the trailing field enumeration is long but does convey return content in the absence of an output schema.

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 one-parameter read with no output schema, the description is nearly sufficient: it names the key, the scope, and the returned fields. The only real gap is the missing contrast with get_product, which matters given both exist in this sibling set.

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?

There is one parameter at 100% schema coverage, and the schema already documents it with an example ('/asset/<slug>'). The description reinforces that the slug comes from the page address but adds no format or validation detail beyond the schema, so baseline 3 applies.

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 gives a specific verb and resource ('Read one live Harashsuq listing') and pins the lookup key ('by the slug in its page address'), which clearly separates it from the plural search_assets. It never names get_product, however, so the asset-vs-product boundary is left for the agent to infer from tool names alone.

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?

Single-record retrieval by slug implies the when-to-use case (you already have a slug; otherwise search), but the description never says so explicitly and offers no exclusion against search_assets, get_product, or get_order_status. The agent must infer the routing rule.

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