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

The annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is fully covered. The description's only added behavioral detail is 'Mindbody calls: 1' and the underlying endpoint, which is mildly useful for cost awareness but says nothing about result ordering, pagination limits, or default filtering (e.g., that sellOnline defaults to false and returns all products).

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 body is a single efficient sentence, but the front-loaded boilerplate ('Get Products — GET /sale/products', 'Mindbody calls: 1.') restates the title and exposes transport trivia before the actual meaning. Trimming that would make the sentence fully front-loaded.

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 10-parameter filter tool with no output schema, the definition should hint at what a product record contains (id, name, price, barcode) since no structured field describes the response. Annotations cover the read-only/idempotent profile and the schema covers inputs, so the gap is moderate rather than severe.

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?

With 100% schema description coverage across all 10 parameters, the schema already explains every field, including the locationId tax default and the sellOnline behavior, so baseline 3 applies. The description adds no additional parameter semantics such as how searchText interacts with productIds or category filters.

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?

States a specific verb and resource ('Get retail products') plus a scope qualifier ('available for purchase at a site'), which is more informative than a restated title. It does not, however, distinguish itself from the closely named sibling get_products_inventory, leaving an agent to guess which one returns sellable catalog items vs. stock levels.

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 when-to-use guidance, no exclusions, and no mention of the obvious alternative (get_products_inventory) despite it being in the sibling list. The phrase 'available for purchase at a site' implies a retail-catalog context but never states when to prefer this tool over the inventory or sales tools.

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