Get DNS product availability

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

Beyond the readOnly/openWorld/idempotent annotations, the description discloses the exact stock enum values, the fallback to city shop addresses when SKU-level lists are empty, and the effect of toggling includeStores. This is rich behavioral context that helps an agent predict responses.

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?

Four dense, front-loaded sentences cover purpose, when to use, return enum, fallback behavior, and an option. No filler or 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?

For a tool with no declared parameters and no output schema, the description does a good job of explaining return values and fallback behavior. It loses a point because it references an includeStores parameter that is absent from the schema, leaving an agent uncertain how to actually apply that instruction.

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 input schema declares zero parameters, yet the description says 'Set includeStores=false', implying a parameter that the schema does not expose. This is misleading for invocation because an agent cannot legitimately pass includeStores according to the schema. The 0-parameter baseline of 4 is therefore not met.

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 the tool reports stock/pickup availability for the current city and will return a specific stock enum, which makes its core function evident. It does not explicitly differentiate from sibling tools such as dns_product_details or dns_list_stores, though it does say to prefer it over marketplace offers.

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?

It gives clear context: use for current-city DNS availability and prefer over marketplace offers because DNS is a single retailer. It also provides a conditional usage instruction (includeStores=false), but it does not name sibling alternatives or spell out when not to use the tool.

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