wb_seller_info

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

With no annotations provided, the description carries the full disclosure burden. It adds the useful behavioral trait that any token works, but it never explicitly states that the call is read-only/idempotent or what happens on failure. Adequate for a simple info endpoint, but not rich.

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 two short sentences and front-loads the core meaning. The Russian parenthetical '(информация о продавце)' merely repeats 'Seller info' in another language, adding slight redundancy, but overall there is no significant waste.

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 zero-parameter, no-output-schema, no-annotation tool, the description covers the essentials: what it returns (name, profile ID) and auth behavior (any token). It could add an explicit read-only statement, but nothing critical is missing given the tool's simplicity.

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?

There are zero parameters, so the schema is vacuously 100% covered and no parameter documentation is needed. The description instead adds relevant non-parameter information (returned fields), so it wastes nothing on parameters.

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 the resource (seller) and the precise output fields (name, profile ID), which distinguishes it from nearby siblings like wb_seller_rating and wb_list_shops. Lacks an explicit verb, but 'Seller info' clearly implies retrieval of seller identity data.

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?

Provides one relevant usage condition: 'Works with any token' tells the agent no special authorization is needed. Does not name alternatives or state when not to use it, though for a zero-parameter info call the usage context is minimal.

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