list_products

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

With no annotations, the description carries the full burden of behavioral disclosure. It only states 'List products' and does not disclose the return format, default limit, inclusion of inactive products, or any side effects. The schema hints at an 'active' filter, but the description does not elaborate on behavior.

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 extremely short and under-specified, essentially repeating the tool name without adding useful detail. While concise, it does not earn its place because it lacks the necessary information an agent needs to make informed decisions.

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 tool has two optional parameters and no output schema. The description fails to explain what the response looks like, any default behavior, or how the parameters affect the result. For a list operation, this is incomplete and leaves critical gaps for an agent.

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 schema provides descriptions for both parameters ('limit' and 'active'), covering 100% of parameters. The description adds no additional meaning about how these parameters affect results, so the schema handles the semantic load. 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 'List products' uses a clear verb and resource, identifying the primary function. It distinguishes from sibling tools like 'list_prices' or 'list_customers' by naming the specific resource, but adds no extra scope or context beyond the tool name.

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 usage guidance is provided. The description does not mention when to use this tool versus alternatives like 'get_product' or 'list_prices', nor does it clarify whether this lists all products or only those matching the 'active' filter. There are no exclusions or alternative references.

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