list_products

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

With no annotations provided, the description carries full burden but offers minimal behavioral insight. It implies a read operation ('List') but doesn't disclose permissions needed, pagination, rate limits, or what happens when client_id is null. The output fields are listed but without explanation of their meaning or format.

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 a single, efficient sentence that front-loads the core action. It wastes no words, though it could be more structured by separating parameter guidance from output details.

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 the tool has an output schema (which covers return values), the description's minimalism is somewhat acceptable. However, for a tool with no annotations and 0% schema coverage, it lacks crucial context like authentication needs, error conditions, and parameter semantics, making it incomplete for safe agent use.

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 description coverage is 0%, so the description must compensate but only partially does. It mentions 'for a client' which hints at the client_id parameter's role, but doesn't explain the parameter's purpose, format, or implications of the null default. The description lists output fields, which adds some context beyond the input 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 action ('List all products') and target resource ('for a client'), with specific output fields mentioned. It distinguishes from siblings like 'get_product_tree' by focusing on listing rather than hierarchical structure, though it doesn't explicitly contrast with all product-related tools.

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 like 'get_product_tree' or 'configure_product_strategy'. The description mentions 'for a client' but doesn't specify prerequisites, exclusions, or contextual triggers for selection.

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