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

No annotations are provided, so the description carries the full disclosure burden. It discloses the exact categories of returned data, availability enum values, price semantics, outbound-link classification, and the canonical-URL-only constraint. It does not discuss error cases or rate limits, but for a public read operation this is reasonable.

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 a single, information-dense sentence that front-loads the action and resource. It lists many relevant details without filler, though the length and nested clauses make it slightly dense to parse.

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 must explain the return shape, and it does so thoroughly by listing fields and enums. For a two-parameter public fetch tool, this is largely complete; minor omissions like error behavior are not critical here.

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?

Input schema covers both parameters with descriptions: slug and storefront, including examples and enum values. The tool description does not add much beyond 'specific storefront', but since schema coverage is 100%, the baseline of 3 is appropriate.

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 uses a specific verb ('Fetch') and identifies the exact resource: full public details for one Mamanida product on a specific storefront. It enumerates the return fields, making the tool's purpose unambiguous and clearly distinct from siblings like search_products or compare_products.

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 gives clear context: use this tool when you need detailed, single-product data for a specific storefront using slug and storefront. It does not explicitly name alternatives or when-not-to-use conditions, but the singular 'one product' scope and the canonical-URL constraint imply the right selection.

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