fiken_list_products

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

The description only discloses that 'amounts are in cents', which is a useful detail. However, it fails to mention pagination behavior (page, pageSize), that the result is a list of product objects, or any other behavioral traits. With no annotations, the description carries the full burden and is insufficient.

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 very short (two sentences) and to the point. It wastes no words. However, it could be more informative without being verbose, e.g., mentioning pagination or filtering. Still, it is concise.

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 11 parameters and no output schema, the description is incomplete. It does not explain the return format (a list of products), pagination details, or summarize the filtering capabilities. The 'cents' note is helpful but insufficient for an agent to fully understand the tool's behavior.

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 100%, so all parameters are documented in the schema. The description adds no extra meaning for parameters beyond that. The 'Amounts are in cents' note is about return values, not parameters. Baseline of 3 is appropriate as the schema does the work.

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 products') and the context ('for a company'). The verb 'list' distinguishes it from the sibling 'fiken_get_product' which retrieves a single product. However, it does not explicitly state that it returns multiple products or that it is a paginated list.

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. For example, it does not mention that to retrieve a single product one should use 'fiken_get_product' or that filtering options are available. The description leaves the agent guessing about the appropriate use case.

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