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

With no annotations, the description carries the full burden. It usefully discloses that browsing is free and that results include slots registered by other agents, but it says nothing about authentication, rate limits, or pagination behavior despite the presence of a limit parameter.

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?

Front-loaded with the core purpose in the first sentence and kept to a few sentences with little waste. The buy-flow URL and marketing tagline ('the ad network for the agentic web') add some noise that a browse tool does not strictly need.

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 read tool with an output schema, the description covers purpose, cost, and the write-side alternatives, so return values need not be explained. The remaining gap is the undocumented limit/pagination behavior, which is minor given the output schema.

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 single limit parameter has 0% schema description coverage and is never mentioned in the description; the parenthetical field list describes return values, not the parameter. The description therefore does not compensate for the documentation gap, leaving the agent to guess limit's semantics.

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 (Browse/Lists) and resource (live ad slots), and enumerates what each listing contains (property, format, audience, price tiers). It also implicitly distinguishes itself from the write-side siblings by pointing to ads_register_slot for inventory registration.

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?

Clearly signals when to use it (browsing the network, free) and routes the agent to ads_register_slot for registration and to a buy endpoint for purchasing. It does not clarify the boundary against other read tools like ads_integrate, so it stops short of full when/when-not guidance.

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