Browse DNS brand products

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

Annotations already declare readOnlyHint, openWorldHint, and idempotentHint, covering the safety profile. The description adds only a little behavioral context, such as the 'search fallback' role, but does not explain output shape, pagination, or the effect of compact/rich modes beyond what the schema already provides.

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 very short and free of filler, and the core point is front-loaded. It is slightly too terse, almost a noun phrase rather than a complete sentence, but it earns its place without redundancy.

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 should explain more about what the returned products look like, especially since the tool supports compact/rich payloads, sorting, and pagination. The current one-liner leaves the agent inferring response structure and behavior from parameter names and hints.

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 50%, and the description does not compensate for the undocumented parameters (page, sort, limit). It only repeats the notion of a brand name, which the schema already documents with examples. No additional meaning is added to the parameter list.

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 identifies the resource (products for a brand) and the action (browse/list), which is distinct from search or related-product tools. The parenthetical 'brand page or search fallback' adds context but does not explicitly contrast it with sibling tools like dns_search or dns_related_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 phrase 'brand page or search fallback' gives clear context for when this tool is appropriate: browsing a specific brand's products or as a fallback after a search. However, it does not explicitly state when not to use it or name an alternative, such as using dns_search for non-brand-specific queries.

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