wb_advert_subjects

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It communicates that the result is a set of advertising-related subjects, but it does not state whether the operation is read-only, what the response shape is, or whether any pagination or filtering behavior exists. It is not misleading, but it is quite sparse.

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 one short sentence with no filler and is front-loaded with the core meaning. The parenthetical Russian clarification adds useful context for the target domain without bloating the text.

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 no-parameter lookup tool, the description is nearly sufficient, but it leaves ambiguity against sibling tools and provides no usage or response context. It is minimally viable but not complete.

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 tool has zero parameters and the input schema is an empty object, so there are no parameter semantics for the description to clarify. Per the baseline for zero-parameter tools, this dimension is already satisfied.

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 states a specific resource ('subjects') and its purpose ('for ad campaigns'). The word 'available' implies a list/read operation, though no explicit verb like 'list' or 'get' is used. It is distinguishable from generic subject tools like wb_subjects_search because it scopes the subjects to ad campaigns.

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?

No guidance is provided on when to use this tool versus alternatives such as wb_subjects_search or wb_subject_charcs. The phrase 'for ad campaigns' gives a weak hint, but there is no explicit context, prerequisite, or exclusion to guide an agent's choice.

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