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

Annotations already cover readOnlyHint, idempotentHint, and destructiveHint, so the safety profile is known. The description adds useful behavioral detail beyond annotations: archived/flagged listings are included by default, is_active true filters to live only, and moderation flags are returned.

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 concise sentences front-load the core purpose, then provide the key default behavior, the filter, and the returned fields. Every sentence adds valuable information without redundancy.

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 paginated list tool with all parameters documented in the schema, the description is complete. It names the returned fields, explains the default inclusion of archived/flagged listings, and notes pagination, so an agent has enough context to invoke it correctly even without an 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?

Schema coverage is 100%, so the baseline is 3. The description adds extra meaning by clarifying that the default behavior includes flagged listings and that is_active: true narrows to live listings only, which goes slightly beyond the schema's 'active status' phrasing.

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 clearly states the tool lists the bound seller's product listings with pagination, which is a specific verb and resource. It also distinguishes itself by noting the inclusion of archived/flagged listings by default, so an agent can tell it apart from seller_get_listing or seller_list_orders.

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 gives clear context: it is the list endpoint for the bound seller's product listings, paginated, with filtering by active status. It does not explicitly name alternative tools like seller_get_listing for single-list access, but the usage context is unambiguous enough for correct selection.

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