Seller Ads

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety and mutation profile is fully covered elsewhere. The description adds only the shape of the payload (profile fields + active ads), with nothing about pagination behavior or how many ads come back.

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?

Two tight sentences with no filler, and the payload contents are front-loaded ahead of the use case. It is appropriately sized for a simple lookup tool.

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?

An output schema exists, so return values need not be explained, and the description covers what data arrives. However, for a tool with a free-text ad search and limit/offset paging, the description never mentions pagination or how the query parameter scopes results, and it never positions itself against siblings.

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 only 50%: login and query are documented in the schema, while limit and offset carry no description anywhere. The prose says nothing about parameters, so the pagination controls are left entirely to convention with no compensation from the description.

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 names the resource precisely — a seller's profile (registered since, verified, business plan) plus their active ads — which is far more informative than the bare tool name. It lacks an explicit verb and never differentiates itself from siblings like get_ad or search, which is the only thing separating it from a 5.

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?

'Handy to tell a private person from an agency or reseller' gives one concrete intended use, so usage is implied rather than absent. There is no guidance on when to prefer this over get_ad or search, and no exclusions or preconditions are stated.

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