list_products

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

No annotations are provided and the description does not disclose any behavioral traits such as whether the operation is read-only, paginated, filtered, or what data it returns. The phrase 'The product catalogue' is entirely static and offers no insight into how the tool behaves when invoked.

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 four words long, but brevity here is under-specification rather than conciseness. It lacks a verb, and a proper tool description should at least say 'List products in the catalogue.' The structure does not front-load any actionable information.

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?

For a zero-parameter tool with no output schema, the description is still inadequate. It does not explain what a product catalogue entry contains, whether the result is a list or a single item, or how this tool differs from the several other list_* tools. An agent would have to guess at the return value and 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 tool takes zero parameters, and the schema is empty, so there are no parameter semantics to document. Per the rubric, a zero-parameter tool gets a baseline of 4, and there is no gap for the description to compensate for.

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 'The product catalogue' is a noun phrase that identifies the subject but does not state any verb or action. It essentially restates the resource implied by the tool name 'list_products' without clarifying that the tool returns a list of products. This is close to a tautology and does not distinguish it from other list 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?

There is no guidance on when to use this tool versus the many sibling list tools such as list_clients, list_invoices, list_orders, or list_tickets. The description provides no context about typical use cases, exclusions, or alternatives, leaving the agent to infer everything from the name alone.

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