tally_list_stock_items

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

With no annotations provided, the description carries full burden and delivers extensively. It discloses pagination behavior ('client-side over a full fetch... small pageSize does not make the call cheap'), error semantics ('returns nothing... is a real answer rather than an error'), return structure ('other value appears under fields with TallyPrime own field names'), a safety note about text fields not being instructions, and a strict read-only guarantee. This is exemplary transparency beyond the name and schema.

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 well-structured with labeled sections (WHEN TO USE, PAGINATION, etc.) and a clear opening sentence. While it is longer than strictly necessary, each section addresses a distinct concern (purpose, verification status, performance, security, read-only), so it earns its length. The front-loaded summary sentence makes the core purpose immediately visible.

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 tool with no output schema and no annotations, the description is remarkably complete. It covers return behavior, error cases (company without stock), pagination performance, field naming, data safety, read-only constraints, and even notes verification status. It goes beyond what is typical, giving an agent all context needed to invoke and interpret results correctly.

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 covers 100% of the four parameters with detailed descriptions, so the baseline is 3. The description does add a PAGINATION section reinforcing that pageSize does not reduce cost, which slightly supplements the schema's own note. However, most parameter meaning already lives in the schema, and the description adds no new per-parameter semantics beyond what is already documented.

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 clear verb+resource: 'List stock items with their closing balance and value.' This specifies both the action and the output. However, it does not explicitly distinguish itself from the sibling tool tally_search_stock_items, though the 'list' vs 'search' naming and the WHEN TO USE section imply a full fetch rather than filtered search.

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 WHEN TO USE section explicitly says 'to see what inventory the company holds,' establishing clear use context. It also provides a fallback: if the tool returns nothing, check tally_get_company to confirm the company keeps stock at all. However, it does not mention alternative tools like tally_search_stock_items or when to prefer those instead, leaving a minor gap.

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