Product brands

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered by structured data. The description adds nothing beyond that — notably it never mentions caching behavior, which is the one non-obvious trait here given the `fresh` parameter's cache-busting semantics. No contradiction, but zero added behavioral context.

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?

It is short, but shortness here is under-specification rather than conciseness: there is no front-loaded verb or object statement, and the entire text is two words restating the title.

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 simple, annotated, one-optional-parameter read tool, the bar is low, but the agent is still left without knowing what a call yields or how it relates to the catalog/category/supplier tools. Annotations cover safety; nothing covers purpose or output shape.

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?

The description says nothing about the single `fresh` parameter, but schema description coverage is 100% and the schema itself explains it as "Skip the local cache." Baseline 3 applies when the schema carries the parameter documentation.

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 is a noun phrase that simply restates the tool name and title ("Product brands.") with no verb, no scope, and no indication of what is returned. An agent still cannot tell whether this lists brands, retrieves brand details, or maps brands to products, nor how it differs from siblings like product_categories or product_suppliers.

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 prerequisites, and no mention of any alternative tool. With closely related siblings (product_catalog, product_categories, product_suppliers, product_stock_history) available, the absence of routing guidance is a real selection hazard.

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