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

The readOnlyHint annotation already discloses the main behavioral trait (safe, read-only operation), and the description's verb 'List' is consistent with it — no contradiction. The description adds no further behavioral context (e.g., determinism, side effects), but for a simple read-only list tool the annotation largely suffices, so the bar is met with only a minor gap.

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?

Two tight sentences with zero filler. The verb and resource are front-loaded in the first sentence, and the sibling differentiation is packed efficiently into the second. Nothing is redundant or extraneous.

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 filtered/paginated list tool with no output schema, the description covers the essential context: what the tool returns, that it is read-only, and how it differs from the closest money-related siblings. It does not itemize every return field (e.g., id, name) or explicitly distinguish it from the other list_* siblings, but the annotated schema and parameter docs fill most of the gap, so the description is complete enough for safe invocation.

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 coverage is 100% and every parameter (from, to, min, max, limit, query, cursor) carries a rich, self-documenting description, which establishes a baseline of 3. The main description adds domain meaning beyond that by noting products include price, cost, stock, and sales totals, which clarifies how the generic min/max 'amount' filters apply — a modest but real increment.

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 opens with a specific verb ('List') and a clear resource ('the business's products'), then states the returned data (price, cost, stock, sales totals). It explicitly differentiates from the sibling tools list_expenses and list_income by pointing out that those handle recorded money-out and money-in, so an agent can immediately tell this tool apart.

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 second sentence gives explicit when-not-to-use guidance: 'for recorded money-out use list_expenses and money-in use list_income.' This directly names the alternatives and the condition that selects them, leaving nothing to inference.

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