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

Annotations already declare readOnly, idempotent, non-destructive, closed-world, so the safety profile is covered. The description adds genuinely new behavioral context beyond them: the required products:read permission, and the warning that supply and pricing fields may be incomplete and the record is not sellable. It does not say what happens when the product_id is unknown or in another owner's catalogue.

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?

Three tight sentences, front-loaded with what is read and scoped before the permission and caveat clauses. No filler, though 'in the same owner catalogue as the website' is slightly oblique phrasing for what is essentially an ownership scope constraint.

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 single-parameter read tool with rich annotations and no output schema, the description covers scope, auth, and data-quality caveats adequately. The main remaining gap is the missing explanation of the required identifier format, which is the one thing an agent could get wrong when calling it.

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 description coverage is 0% and the single product_id parameter carries only a pattern and maxLength with no prose. The description never mentions product_id, its expected opaque format (^[a-z]+_[0-9a-f]{32}$), or how to obtain one, so it fails to compensate for the undocumented parameter.

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 (read) and resource (product draft) plus the extra facets it returns: exact version and readiness, scoped to the owner catalogue. It is clearly distinguishable from write siblings like evuun_update_business_product or evuun_publish_business_product, though it never names evuun_list_business_products as the collection counterpart, so the single-vs-list distinction is only implied.

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 permission prerequisite ('requires products:read business permission') and the caveat 'a draft is not a sellable offer' give real usage context, but there is no explicit when-to-use vs when-to-use-something-else routing, e.g. list_business_products for enumeration or get_business_supply for supply detail. Usage is implied rather than stated.

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