list_products

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

No annotations are provided, so the description must fully disclose behavioral traits. It implies a read operation but does not mention pagination behavior, return format, authentication needs, or any side effects. The limit parameter suggests pagination, but the description does not explain this.

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 sentence, but it is under-specified and vague. It does not efficiently convey essential information; it is not concise in the sense of packing meaning, but rather terse and unhelpful.

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 simple tool (one optional parameter, no output schema), the description should clearly state what the tool returns (a list of products). It does not, leaving the agent without a complete picture of the tool's I/O 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?

The input schema has one parameter (limit) with no description coverage (0%). The tool description completely fails to explain the limit parameter or how it affects the results. This is a critical gap.

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 uses the ambiguous verb 'Inventory' instead of a clearer term like 'list' or 'retrieve'. It identifies the resource as 'product / service catalog billable on invoices', which provides some specificity but does not clearly state that the tool returns a list of items.

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?

The description provides no guidance on when to use this tool versus sibling list tools (e.g., list_animals, list_appointments). There is no mention of appropriate contexts, exclusions, or alternatives.

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