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

With no annotations provided, the description carries the full burden of behavioral disclosure and does so thoroughly. It explains what is returned in list mode vs. detail mode, lists the metadata fields, describes the structured body components, and explicitly states that retailer and affiliate URLs are never returned — a useful negative guarantee.

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 dense but well-structured: it opens with the core purpose, then covers both invocation modes in logical order, then integration and exclusions. Every sentence adds value, and no information is wasted or redundant with the 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?

Given there is no output schema, the description does an excellent job of explaining return contents: metadata fields for listings and structured body elements for single guides. It also covers locale behavior, filtering, and the integration path with `search_products`, making the tool effectively self-documenting for an agent.

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?

Schema coverage is 100%, so the baseline is 3, but the description adds meaningful semantics beyond the schema: `guide` is a slug from the listing, `topic` filters the listing, and `storefront` determines the localized language edition. This enriches the agent's understanding of how parameters change tool behavior.

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 states a specific verb-resource pair ('List or read Mamanida buying guides') and distinguishes the two invocation modes (listing vs. reading a single guide). It also differentiates this tool from product-focused siblings by emphasizing editorial guide content and the guide → category → product path.

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 explicit context for when to use each mode: omit `guide` to list, provide `guide` to read a specific localized edition. It also names the intended downstream tool, `search_products`, and how to pass `category_slug`, though it does not explicitly state when to prefer sibling tools like `get_product` or `list_categories`.

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