authorized_seller_list

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

The description adds that the tool lists 'saved' authorized sellers, indicating it returns existing data. The annotation readOnlyHint=true already signals a safe read operation. No further behavioral details (e.g., pagination, authorization) are provided, but this is adequate for a simple list tool.

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 concise sentences: the first states the action, the second gives usage examples. No extraneous information; front-loaded and efficient.

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?

Given a simple 3-parameter tool with readOnlyHint and no output schema, the description covers the purpose and typical usage scenarios. It could optionally mention that it returns a list of seller names, but overall it is complete enough.

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 has 100% description coverage, so the schema alone documents all parameters' meanings. The description does not add any parameter-level details beyond what is in the schema, so baseline 3 is appropriate.

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 specifies the verb 'List' and the resource 'saved authorized sellers for a brand'. It provides concrete user query examples ('who are my authorized sellers for X'), clearly distinguishing it from sibling tools like authorized_seller_set (write) and unauthorized_sellers (different set).

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?

The description includes explicit usage cues: 'Use when the user asks...' with three example queries. While it does not state when not to use, the examples clearly delineate the tool's purpose, making it easy for an agent to match.

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