get_stock_items

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

Although annotations already establish this as a safe read (readOnlyHint=true, openWorldHint=false), the description adds substantial behavioral detail beyond them: GSTAPPLICABLE is computed by Tally and cannot be set, unset fields come back blank/empty, GSTDETAILS is null when no entry exists, and only the latest applicableFrom GST entry is returned rather than full history. That is exactly the kind of read-shape and edge-case disclosure an agent needs.

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 purpose and the core fields (NAME, PARENT, CLOSINGBALANCE) are front-loaded, and every subsequent clause carries real information rather than filler. It is a long, dense compound construction with several parentheticals, which costs some readability, but little of it is expendable given there is no output schema.

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?

With no output schema and no parameters, the description carries the full burden of describing the return value, and it does so thoroughly: enumerated fields, null/blank semantics, read-only fields, and the date-versioning caveat. An agent has enough to interpret results without further documentation.

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, so per the baseline there is nothing for the description to add; the schema is empty and the description correctly spends its space on output semantics instead. No parameter-level ambiguity is possible.

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?

States a specific verb and resource ('Get all stock items from TallyPrime') and the scope ('all'), so an agent knows this returns the stock item master list rather than an aggregate. It does not explicitly distinguish itself from near-siblings such as get_stock_summary or get_reorder_status, leaving the agent to infer the difference.

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 explicit when-to-use guidance, no stated prerequisites (e.g. company/period must be set), and no routing to alternatives like get_stock_summary. The only cross-references (create_stock_item/update_stock_item) explain where GST detail fields come from, not when to call this tool.

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