create_material_in

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

The description goes well beyond the annotations: it reveals that this is a memorandum posting without real accounting impact, that it uses Tally's 'Multi Consumption Voucher View' shape, that the template is extrapolated and unverified, and that users should verify carefully. It also documents a known failure mode (LINEERROR 'Voucher date is missing') and the exact remedy (set_period + retry). This is rich behavioral disclosure beyond the readOnly/destructive hints.

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?

Every sentence earns its place: the first defines the tool, the next gives the job-work context and caveat, then the godown warning, then a concrete troubleshooting path. It is long but information-dense, front-loaded with the core purpose and structured so the warnings and error handling are easy to locate.

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?

No output schema exists, and the description doesn't describe the success response, but it does cover the most important operational context: prerequisites (party ledger, items, date), conditional requirements (godown), and failure recovery (set_period, voucherNumber fallback). For a creation tool, error modes are as important as success output, and those are thoroughly covered; only a brief note on expected success behavior is absent.

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%, so each parameter already has a description. The tool description adds value on top by advising to 'pass godown on every item' when godown/batch tracking is enabled, and by explaining the voucherNumber auto-numbering caveat and the EXCEPTIONS:1 retry strategy. This supplements the schema rather than repeating it.

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 and resource: 'Create a Material In voucher in TallyPrime' and immediately defines its exact purpose: recording stock received back from a job worker or party holding material, with the key distinction that it is job-work memorandum tracking, not a purchase. This differentiates it clearly from purchase vouchers and other sibling tools like create_material_out or create_rejections_in.

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 gives strong contextual guidance: it explains when this voucher type is appropriate (job-work returns, non-purchase tracking) and explicitly flags when to be cautious (godown/batch companies, active-period issues). It does not name specific alternative tools for explicit when-not-to-use, but the 'not a purchase' statement and the job-worker framing provide enough direction for an agent to select it over siblings.

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