summarize_product_location_flows

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

No annotations are provided, so the description carries the full burden. It implies a read-only aggregation but does not disclose the scope of data considered, time range, grouping behavior, or whether all locations are included. The phrase 'summarize entries, exits and internal location flows' gives some behavioral detail but not enough.

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 succinct sentence with a front-loaded verb and resource. It avoids padding, though the brevity leaves notable gaps in usage and parameter guidance.

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 existence of many similar sibling tools and no annotations, this description is too thin. The output schema helps with return values, but the tool still lacks contextual guidance about when to use it, what the limit affects, and how it differs from summarize_product_moves.

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%, and the description adds no real parameter meaning. It only restates the product concept that is already in the schema, and the limit parameter is completely unexplained.

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 verb (summarize) and resource (product location flows), and specifies the scope: entries, exits, and internal location flows. It does not explicitly differentiate from sibling summarize_product_moves, but the core purpose is unambiguous.

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?

There is no guidance on when to prefer this tool over summarize_product_moves, search_stock_moves, or other location-related tools. The description only explains what the tool does, not when to use it or when to avoid it.

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