products_list

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

The description adds that the output shape is consistent with the voog://products resource. The annotations already fully declare the tool as read-only, non-destructive, and idempotent, so the behavioral additions are modest.

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 sentences plus a brief note, all front-loaded with the essential purpose. Every sentence adds value with no 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?

The description lists the returned fields, explains the optional filter, and references the consistent resource shape. It provides sufficient context for effective use 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% with descriptions for both parameters. The description restates the category_id filtering logic without adding significant new meaning beyond the schema.

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 all ecommerce products on the Voog site, specifies which fields are returned, and distinguishes itself from product_get for per-variant stock details.

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?

It explicitly notes the tool is read-only and advises using product_get when per-variant stock is needed. It also explains the category_id filter, but does not explicitly list when not to use it beyond the variant case.

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